speckit-specify

To turn a natural language feature description into a structured specification, provide your feature text to automatically generate a spec directory, populate a markdown template with requirements and success criteria, and validate readiness for planning workflows.

Feature specification bootstrapping automatically creates a structured spec directory and markdown file from plain text, applying a completeness checklist to validate quality and reduce ambiguity before the planning phase begins.

You generate a planning-ready feature spec by parsing a plain text idea to create a concise short name, automatically writing feature.json, and validating the output against a completeness checklist to ensure readiness for the next phase.

Feature specification generation supports custom workflows by running optional project-defined pre- and post-processing hooks when present and enabled, using a template-based structure to populate user scenarios and functional requirements.

You can use natural language to create feature directories and spec files automatically by parsing a description to generate a concise short name, creating the specs/<generated-id>-<short-name>/spec.md path, and writing the feature.json metadata.

If your feature description lacks detail during spec generation, the process optionally asks up to three targeted clarification questions to gather missing information before validating the spec against a completeness checklist and reporting readiness.