speckit-specify

Feature specifications are generated by transforming plain-language descriptions into structured, plan-ready specs. The process creates a feature directory under specs with a template spec file, validating sections like user scenarios, requirements, and success criteria for immediate planning readiness.

Writing a feature spec from plain language involves automating the transformation into a machine-readable specification. This generates a complete spec skeleton including assumptions, constraints, and success criteria, while surfacing [NEEDS CLARIFICATION] markers to resolve ambiguities before planning begins.

Requirements validation checks the spec against quality criteria to ensure planning readiness. It surfaces [NEEDS CLARIFICATION] markers when ambiguities exist and produces a quality-check checklist covering user scenarios, requirements, and success criteria sections.

A spec-kit project with a .specify workflow is required to generate ready-to-plan feature specifications. The tool creates a dedicated feature directory under specs and persists a reference path for downstream planning steps within this specific project structure.

Generated specifications include structured sections for user scenarios, requirements, success criteria, assumptions, and constraints. These sections form a complete feature spec skeleton derived from the natural language input, ensuring comprehensive coverage for downstream planning.

[NEEDS CLARIFICATION] markers appear during specification validation when the natural language input contains ambiguities. They are surfaced intentionally to highlight missing details that must be resolved before the spec can be considered ready for planning.