What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and error-prone, often producing ambiguous requirements that derail planning. This Skill converts a natural language feature description into a structured spec file with user scenarios, functional requirements, and measurable success criteria. ## Core Features & Use Cases - Spec Generation: Creates a numbered feature directory under specs/ and writes a spec.md from the resolved spec template, persisting the path in .specify/feature.json for downstream commands. - Quality Validation: Builds a requirements checklist, validates the spec against content and completeness criteria, and iterates up to three times to fix failures. - Clarification Handling: Limits ambiguity to a maximum of three [NEEDS CLARIFICATION] markers and presents structured multiple-choice questions to resolve them. - Extension Hooks: Runs optional and mandatory before_specify and after_specify hooks defined in .specify/extensions.yml, such as automatic git branch creation. - Use Case: A product manager types a feature idea like "add OAuth2 login for the mobile app" and receives a ready-to-plan specification with acceptance scenarios and success metrics. ## Quick Start Ask the agent to run /speckit-specify followed by a plain-language description of the feature you want specified.
