speckit-specify

To convert natural-language feature ideas into structured specifications, describe your feature in plain language and the system generates a plan-ready spec file with sections like Scope, Requirements, User Scenarios, and Acceptance Criteria.

Generating a feature spec with acceptance criteria from plain text involves loading templates and validating quality with a built-in checklist. The process resolves ambiguity through optional clarification questions to ensure plan-ready output.

To create a spec directory and spec.md file for product teams, you run the specification generation process which structures your plain-language input into a formal document under the specs/ directory using predefined templates.

Yes, you can validate feature specifications and resolve ambiguity using a built-in quality checklist. The system supports optional clarification questions during generation to ensure the final spec meets plan-ready requirements.

The specification generation process supports executing optional extension hooks during creation and optional after-hook handling upon completion, allowing you to extend the workflow when producing the final SPEC_FILE.

A plan-ready specification generated from plain language includes structured sections for Scope, Requirements, User Scenarios, and Acceptance Criteria, ensuring the final SPEC_FILE is validated and ready for downstream planning.