What problem does it solve? Turning a rough feature idea into a complete, testable specification is slow and error-prone. This Skill converts a natural 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/ with a spec.md built from the resolved spec-template, covering user scenarios, 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 for ambiguous points. - Extension Hooks: Supports before_specify and after_specify hooks from .specify/extensions.yml, including optional git branch creation. - Use Case: A product manager types a feature idea like "add OAuth2 login" and receives a ready-to-plan specification at specs/003-oauth2-login/spec.md with a validated checklist, ready for the clarify or plan phase. ## Quick Start Ask the agent to create a feature specification by describing your feature, for example: create a spec for adding user authentication with OAuth2.
