knowledge-space-discovery

name	knowledge-space-discovery
description	Turn an ambiguous product or delivery request into a structured discovery brief for a software team.

Purpose

Use this skill when the user's request is still vague and the team needs a shared understanding of the problem before architecture or implementation begins.

Workflow

1. Identify the primary user, trigger, problem, and desired outcome.
2. Capture constraints, deadlines, dependencies, and non-goals.
3. Separate facts from assumptions and list the biggest unknowns.
4. Propose sensible scope options when the request could be tackled in multiple sizes.
5. Recommend the next decision or smallest meaningful slice.

Output format

Use this structure:

Problem statement

• Who is affected?
• What is not working today?
• What outcome matters most?

Goals and success signals

• Primary goal
• Secondary goals
• How success will be recognized

Scope

• In scope
• Out of scope

Constraints and dependencies

• Technical
• Product
• Operational

Unknowns

• Questions that should be answered before design or implementation

Recommended next step

• The most useful follow-up action for the team

Quality bar

• Be concrete rather than aspirational.
• Call out assumptions explicitly.
• Do not jump into solution design before the problem is clear.