speckit-specify

To turn a natural language feature idea into a structured specification, describe the feature in plain text. The system generates a planning-ready spec with user scenarios, functional requirements, and measurable success criteria.

Generating a feature specification and creating a branch happens simultaneously by running the specify command. It creates a short-named feature branch and writes the structured spec to a file using your project template.

Yes, you can validate feature requirements before product planning. The system checks the written specification against a validation checklist and iterates to fix issues automatically over a limited number of passes.

The best way to write technology-agnostic success criteria for product planning is to use a template-driven generation process. This ensures success criteria remain measurable and testable without tying them to specific implementation details.

A project template is required to generate feature specs. The system uses template-driven document generation to write the structured specification to a file, ensuring the output aligns with your project's established format.

The automated quality validation for feature specs is limited to a fixed number of iteration passes. It validates the written specification against a checklist and stops attempting fixes once it reaches the maximum pass limit.