speckit-specify

To convert a natural-language feature idea into a structured specification, provide your feature details after the specify command. The tool generates a testable feature spec from your text and writes it into a newly created spec directory using a consistent template.

The best way to scaffold a feature spec directory is to use this tool, which automatically creates a new directory under specs/ and writes spec.md from a project template. You can also provide a custom directory path to control where the feature specification files are persisted.

The quality validation loop checks requirements by generating a checklist and validating the specification against it. It iteratively updates the spec to address issues, running up to three validation passes to ensure the requirements are fully testable and ready for planning.

Yes, you can run extension hooks for feature specification generation. The tool runs configured before_specify hooks prior to writing the spec, and optionally executes after_specify hooks afterward to integrate the newly created specification directly into your existing workflow automation.

No dependencies are required to use this feature specification tool. It operates independently to convert natural-language descriptions into testable specifications, meaning you can start scaffolding project specs and running quality validation without installing additional packages.

After the specification is validated and ready for planning, the tool persists the resolved feature directory path and reports readiness. This output allows you to seamlessly proceed to subsequent clarify or plan steps within your project management workflow.