What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and error-prone. This Skill converts a plain-language feature description into a structured spec.md file inside a spec-kit project, complete with user scenarios, functional requirements, success criteria, and a quality checklist. ## Core Features & Use Cases - Spec Generation: Creates a numbered feature directory under specs/ and writes a spec.md from the resolved spec-template, with at most 3 [NEEDS CLARIFICATION] markers for genuinely ambiguous decisions. - Quality Validation: Generates a requirements checklist and iteratively validates the spec against content quality, requirement completeness, and feature readiness criteria (up to 3 iterations). - Extension Hooks: Executes before_specify and after_specify hooks declared in .specify/extensions.yml, and persists the feature directory to .specify/feature.json for downstream commands like /speckit-plan. - Use Case: A developer types a feature idea such as "add OAuth2 login to the API" and receives a ready-to-plan specification with measurable, technology-agnostic success criteria. ## Quick Start Ask the assistant to create a feature specification by describing the feature you want, for example requesting a spec for user authentication with OAuth2.
