problem-statement-refiner
Purpose
Turn a vague idea, pain point, or project brief into a crisp problem statement with objective, scope, stakeholders, constraints, and success criteria.
Trigger this skill when
- The request is broad, solution-first, or unclear about the actual problem.
- A repo or project starts with a one-paragraph brief, issue, or verbal idea.
- You need a sharper statement before requirements, design, or estimation.
Expected inputs
- raw brief
- business context
- user/stakeholder context
- known constraints
- known goals
Deliverables
- refined problem statement
- goal statement
- scope draft
- explicit assumptions
- open questions
- success criteria
Operating procedure
- Extract the current pain, desired outcome, affected users, and business context.
- Separate symptoms from root problem.
- Rewrite the problem in one sentence using actor + need + obstacle + impact.
- List scope boundaries, constraints, assumptions, and unknowns.
- Define measurable success criteria where possible.
- Surface the top unresolved questions that block good requirements.
Quality gates
- Distinguishes problem from proposed solution.
- Names the affected actor(s) and operational/business impact.
- Contains scope and non-scope.
- Includes unresolved questions instead of guessing.
Handoff targets
- requirements-interrogator
- functional-vs-nonfunctional-splitter
- assumption-extractor
Output style
- Be explicit about uncertainty.
- Prefer short, testable statements over long prose.
- Surface risk and ambiguity instead of guessing.
- Separate facts, assumptions, constraints, and open questions.
Failure modes to avoid
- Do not invent stakeholder intent.
- Do not convert preferences into mandatory requirements without evidence.
- Do not hide unresolved ambiguity behind polished wording.
- Do not collapse functional, non-functional, and business rule concerns into one blob.
Minimum output skeleton
## Summary
## Findings
## Structured outputs
## Assumptions
## Constraints
## Open questions
## Recommended next skill
1---2name: problem-statement-refiner3description: problem-statement-refiner4---5# problem-statement-refiner67## Purpose8Turn a vague idea, pain point, or project brief into a crisp problem statement with objective, scope, stakeholders, constraints, and success criteria.910## Trigger this skill when11- The request is broad, solution-first, or unclear about the actual problem.12- A repo or project starts with a one-paragraph brief, issue, or verbal idea.13- You need a sharper statement before requirements, design, or estimation.1415## Expected inputs16- raw brief17- business context18- user/stakeholder context19- known constraints20- known goals2122## Deliverables23- refined problem statement24- goal statement25- scope draft26- explicit assumptions27- open questions28- success criteria2930## Operating procedure311. Extract the current pain, desired outcome, affected users, and business context.322. Separate symptoms from root problem.333. Rewrite the problem in one sentence using actor + need + obstacle + impact.344. List scope boundaries, constraints, assumptions, and unknowns.355. Define measurable success criteria where possible.366. Surface the top unresolved questions that block good requirements.3738## Quality gates39- Distinguishes problem from proposed solution.40- Names the affected actor(s) and operational/business impact.41- Contains scope and non-scope.42- Includes unresolved questions instead of guessing.4344## Handoff targets45- requirements-interrogator46- functional-vs-nonfunctional-splitter47- assumption-extractor4849## Output style50- Be explicit about uncertainty.51- Prefer short, testable statements over long prose.52- Surface risk and ambiguity instead of guessing.53- Separate facts, assumptions, constraints, and open questions.5455## Failure modes to avoid56- Do not invent stakeholder intent.57- Do not convert preferences into mandatory requirements without evidence.58- Do not hide unresolved ambiguity behind polished wording.59- Do not collapse functional, non-functional, and business rule concerns into one blob.6061## Minimum output skeleton62```md63## Summary64## Findings65## Structured outputs66## Assumptions67## Constraints68## Open questions69## Recommended next skill70```