speckit-specify

To turn a natural language feature idea into a structured specification, provide a written description to the Skill. It generates a feature specification file covering user scenarios, functional requirements, and success criteria, while creating a dedicated feature branch.

To ensure feature requirements are testable and complete, this Skill generates a requirements checklist and enforces completeness, clarity, and measurability expectations. It validates the specification quality to guide stakeholders before implementation begins.

Yes, you can run custom pre-spec actions when generating a feature specification. Configure optional or mandatory extension hooks in the `.specify/extensions.yml` project file to execute specific actions before the specification process starts.

Yes, the feature specification process automatically creates a branch. When converting your natural language description into a structured spec, it simultaneously generates a feature branch and the associated spec file for downstream planning.

When writing feature specifications for stakeholder planning, you should include defined user scenarios, functional requirements, success criteria, and key entities. The Skill extracts these elements from your description to structure the planning-ready document.

A limitation of using natural language to generate feature specifications is that the output quality depends on the initial description's clarity. While the Skill enforces testability and completeness via a checklist, vague input may still produce ambiguous requirements requiring manual refinement.