speckit-plan

Automated planning workflows generate design artifacts by applying a predefined plan template to produce files like research.md, data-model.md, contracts/, and quickstart.md, reducing manual coordination and ensuring consistent project setup outputs.

A spec-kit structure is a project organization pattern using a .specify/ directory to manage feature specifications and constitutions. You need it when automating implementation planning to enforce guardrails, evaluate gates, and resolve unknowns before subsequent phases.

Customize the planning workflow by defining optional and mandatory pre- and post-plan hooks in the .specify/extensions.yml file, allowing you to inject custom logic and extension points into the automated design artifact generation process.

No, this planning template targets software projects that follow a spec-kit structure with a .specify/ directory. The automated workflow relies on loading the feature spec and constitution from this directory to evaluate gates and guide planning decisions.

The plan template generates design artifacts including research.md, data-model.md, contracts/, and quickstart.md during the automated planning workflow, providing structured documentation to guide project implementation and setup.

Context-aware planning loads the feature spec and constitution to guide decisions, identifying unknowns that require clarification before proceeding. It evaluates gates and resolves these unknowns to ensure the planning workflow produces consistent, validated design artifacts.