speckit-specify

To generate a feature spec from a natural language description, provide your feature details and run the automated generation process. This converts your text into a complete specification scaffold and outline using standard templates.

Creating consistent feature specifications is best achieved through template-driven automation. This approach validates project hooks and required templates before producing a ready-to-use specification file with structured sections and guidance.

Yes, automated feature spec generation requires a valid project structure. The process validates extension hooks, templates, and outlines within a spec-kit project before producing the final specification file and a planning branch.

Template-driven spec writing validates readiness by checking for pre-execution hooks and required templates before outlining. This ensures the project environment meets structural requirements before generating the final specification file.

Yes, you can convert a plain text feature description into a structured specification outline. The automated process analyzes your natural language input and generates a complete specification scaffold with predefined sections.

When generating a feature specification, expect outputs that include the specification file path and a branch name for planning. These outputs are produced after validating your project's templates and extension hooks.