What problem does it solve?
Vague, ambiguous, or conflicting specifications lead to misaligned implementation, wasted rework, and missed project requirements. This Skill systematically eliminates these gaps by resolving all spec uncertainties before development work begins.
Core Features & Use Cases
- Ambiguity Detection: Scans specification documents for explicit [NEEDS CLARIFICATION] markers and hidden issues like vague unmeasurable terms, conflicting requirements, and untestable acceptance criteria.
- Structured Clarification: Presents targeted multiple-choice questions to users one at a time, coordinates with domain expert (SME) agents for context on ambiguous areas, and updates the spec in real time with accepted answers.
- Guarded Progression: Enforces rules like incrementing requirement IDs, delta change tracking, and a maximum of 8 questions per session, only allowing progression to planning when all critical ambiguities are resolved.
- Use Case: For example, if your project spec includes a vague requirement for "fast performance" without measurable targets or overlapping authentication rules, this Skill will identify the gaps, ask targeted questions, and update the spec with precise, testable requirements before any code is written.
Quick Start
Invoke the clarify-spec skill when your project specification contains [NEEDS CLARIFICATION] markers or has vague, conflicting requirements that need to be resolved before moving to the planning phase.
