problem-statement-refiner
Skill28 starsChanged 8 months agoMITView on GitHub
In this repository105 other files it gives its agents.
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- business-rule-extractorSkill
- catwoe-root-definitionSkill
- constraint-detectorSkill
- critical-thinking-bias-checkSkill
- definition-of-done-drafterSkill
- deliverable-consistency-checkSkill
- edge-case-elicitorSkill
- evidence-gap-reviewSkill
- functional-vs-nonfunctional-splitterSkill
- interview-designSkill
- moscow-prioritisationSkill
- observation-study-planSkill
- pestle-analysisSkill
- porters-five-forcesSkill
- power-interest-gridSkill
- probe-question-generatorSkill
- process-modelling-and-improvementSkill
- process-model-specSkill
- proto-requirements-normalizerSkill
- prototype-elicitationSkill
- pyramid-funnel-diamond-interviewerSkill
- questionnaire-designSkill
- questionnaire-pilot-checkerSkill
- raci-matrixSkill
- raci-rasci-builderSkill
- requirements-conflict-checkerSkill
- requirements-elicitationSkill
- requirements-gap-auditorSkill
- requirements-interrogatorSkill
- requirements-packagerSkill
- requirements-prioritizerSkill
- requirements-quality-checkSkill
- requirements-traceability-starterSkill
- see-i-clarifierSkill
- ssm-analysisSkill
- stakeholder-analysisSkill
- stakeholder-communication-plannerSkill
- stakeholder-registerSkill
- strategy-analysisSkill
- swot-prioritisationSkill
- to-be-process-designerSkill
- use-case-specificationSkill
- value-proposition-analysisSkill
- workshop-designSkill
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Prefer short, testable statements over long prose.
- Distinctive: line 60
Do not invent stakeholder intent.
- Distinctive: line 61
Do not convert preferences into mandatory requirements without evidence.
- Distinctive: line 62
Do not hide unresolved ambiguity behind polished wording.
- Distinctive: line 63
Do not collapse functional, non-functional, and business rule concerns into one blob.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 skillDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

