speckit-specify

To convert a feature idea into a structured specification, provide a natural-language description and the command generates a spec with user scenarios, functional requirements, and measurable success criteria.

Generating testable user scenarios from a feature description requires transforming natural language into structured outputs, creating a spec.md file that outlines specific functional requirements and measurable success criteria.

To set up spec-kit directory conventions, the tool automatically creates a single spec feature directory and spec.md from a template, ensuring downstream planning and task creation can consistently locate the feature.

Yes, you can use optional before_specify hooks to prepare a git branch or add pre-spec behaviors, extending the base feature specification workflow before the actual spec is written.

No dependencies are required to create feature specifications with success criteria; the tool independently validates readiness and generates the structured output directly within the specs folder.

Automated specification templating is not suitable for unstructured feature ideas lacking clear criteria, as it specifically requires natural-language input to generate testable user scenarios and measurable success criteria.