What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and inconsistent across teams. This Skill converts a natural language feature description into a structured spec.md file with user scenarios, functional requirements, and measurable success criteria, then validates it against a quality checklist. ## Core Features & Use Cases - Specification Generation: Parses a feature description into actors, actions, data, and constraints, then writes a spec following the spec-kit template with at most 3 [NEEDS CLARIFICATION] markers. - Quality Validation: Creates a requirements checklist and iterates on the spec (up to 3 passes) until content quality, requirement completeness, and feature readiness checks pass. - Extension Hooks: Executes before_specify and after_specify hooks from .specify/extensions.yml, including git branch creation, and persists the feature directory to .specify/feature.json for downstream commands. - Use Case: A product engineer types a feature idea like "add OAuth2 login for the mobile app" and receives a numbered spec directory (e.g., specs/003-oauth2-login) containing a validated spec.md ready for /speckit-clarify or /speckit-plan. ## Quick Start Ask the agent to run the speckit-specify skill with your feature description, for example: create a specification for adding user authentication with OAuth2.
