speckit-specify

To turn a natural language feature description into a structured specification, provide your feature idea to the speckit-specify Skill. It generates a planning-ready spec, executes a feature branch via the create-new-feature script, and writes the output to your SPEC_FILE.

A validation checklist improves feature specification quality by running an iterative loop to verify the generated spec is complete, testable, and free of unresolved clarification markers before planning begins.

Yes, you can run automated pre-processing hooks before generating a feature spec. The Skill optionally executes project extension hooks before outlining, allowing teams to inject customized automated steps into the .specify workflow.

Yes, speckit-specify works with an existing spec-kit project structure. It is designed for projects utilizing a .specify workflow, allowing you to update existing requirements or start new features within that directory structure.

The best way to automate feature branch creation from requirements is to use a Skill like speckit-specify that triggers the create-new-feature script automatically, generating the branch while writing the planning-ready specification.

To update existing feature requirements in a spec-kit workflow, run the Skill with your updated natural language description. It will load the necessary templates and overwrite the SPEC_FILE with the newly structured specification.