speckit-specify

To convert a natural language feature idea into a structured specification, you provide a short description and the system generates a testable spec with user scenarios, functional requirements, and success criteria. It creates a feature spec directory and spec.md while validating quality through an automated checklist.

Requirements engineering for product planning translates stakeholder needs into measurable success criteria and functional requirements. This process reduces ambiguity before implementation starts by enforcing quality validation and generating required spec sections from a template.

You generate testable functional requirements by processing your short product description through a specification template. The system iteratively improves the output up to three times using an automatically generated checklist to ensure minimal ambiguity and measurable success criteria.

Yes, you can run pre-specification steps by utilizing project-level extension hooks. The system honors before_specify extension hooks to execute optional or mandatory pre-specification actions before generating the feature directory and spec.md file.

Yes, the feature specification process supports configurable directory numbering. When generating the feature spec directory and spec.md file, the system honors configurable directory numbering settings alongside before_specify extension hooks.

The system iteratively improves a generated specification up to three times. It validates spec quality via an automatically generated checklist after converting your natural-language feature idea into a complete, validated, testable specification.