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.md file with user scenarios, functional requirements, success criteria, and a quality checklist. ## Core Features & Use Cases - Spec Generation: Creates a 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, requirement completeness, and feature readiness criteria, with up to 3 clarification questions presented as option tables. - Extension Hooks: Supports before_specify and after_specify hooks from .specify/extensions.yml for branch creation and post-spec automation. - Use Case: A product engineer types a feature idea like "add OAuth2 login" and receives a numbered feature directory containing a stakeholder-ready specification validated against a quality checklist, ready for /speckit-plan. ## Quick Start Ask the agent to run /speckit-specify followed by your feature description, such as "create a specification for adding user authentication with OAuth2".
