speckit-plan

To automate spec-kit project planning, use the speckit-plan workflow to materialize design artifacts like research.md, data-model.md, and contracts. It runs from the project root to generate planning outputs according to defined plan phases.

The implementation workflow produces research.md, data-model.md, contracts, and quickstart guidance. It automatically loads the IMPL_PLAN template and materializes these planning artifacts across Phase 0-2 of the project lifecycle.

To enforce governance during implementation planning, the workflow applies constitution checks and gate validations from the Outline phase through Phase 2. It also enforces pre- and post-execution extension hook checks and cleanly reports executable hooks.

No, this workflow specifically applies to repositories that follow the .specify/ structure. It requires this specific directory layout to load the IMPL_PLAN template and correctly generate the corresponding planning artifacts and contracts.

The best way to guide end-to-end planning from outline through Phase 2 is using an automated workflow that handles constitution checks, gate validations, and extension hook execution. This ensures all functional requirements and artifacts are generated systematically.