speckit-specify

Generating a feature specification from plain language converts your description into structured requirements, user scenarios, and success criteria. The skill writes the output using templates into a designated specs directory for immediate planning use.

Generating user scenarios and success criteria creates a structured specification containing detailed requirements, relevant entities, and assumptions. It includes an automated checklist to validate specification quality through a structured re-validation loop.

Yes, writing feature specifications requires a spec-kit compatible directory structure. The skill outputs generated specifications directly into a specs directory and can execute optional before_specify extension hooks to prepare the workflow environment.

Yes, you can use optional before_specify extension hooks to prepare git branches or influence the workflow before specifying requirements. These hooks execute prior to the template-based spec writing and quality validation processes.

Quality validation works by generating an automated checklist for the feature specification and iterating with limited clarification prompts. This checklist-driven loop validates requirements and scenarios until the spec meets quality standards.

After you generate an initial feature spec from a plain language description, the output is ready for downstream clarification and planning steps. The created specification can be directly processed using /speckit-clarify or /speckit-plan workflows.