speckit-specify

Feature specification generation parses a natural-language feature description to produce a structured, testable spec.md file with required sections and measurable success criteria. It also generates a requirements checklist to validate specification quality before planning.

Validating feature requirements before planning involves generating a requirements checklist at specs/<feature>/checklists/requirements.md and evaluating the specification against it. The validation iterates up to three times until quality criteria pass.

Yes, pre-flight extension hooks can be configured and executed before specification generation. Optional and mandatory before-specify hooks defined in .specify/extensions.yml are supported, including branch setup when available.

The best way to format feature specifications for iterative product planning is using a standardized template that creates a dedicated spec directory. This generates a spec.md with required sections and a parallel requirements checklist to maintain consistent quality validation.

Feature scoping works without external dependencies or components, operating independently to parse user input and generate the specification directory structure. It relies solely on the provided natural-language feature description to initiate the workflow.