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 plain-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/ with a spec.md built from the resolved spec-template, including user scenarios, functional requirements, success criteria, and key entities. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against content quality, completeness, and readiness criteria, with up to 3 clarification questions presented as option tables. - Extension Hooks: Executes before_specify and after_specify hooks from .specify/extensions.yml, supporting optional and mandatory hook flows 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 complete, validated specification at specs/003-oauth2-login/spec.md ready for /speckit-plan. ## Quick Start Ask the agent to run /speckit-specify followed by a natural language description of the feature you want to specify.
