speckit-plan

To generate implementation design artifacts from a feature specification, run a structured planning workflow that reads your feature spec, resolves clarifications, and outputs data models, contracts, and quickstart guides. This process enforces technical context drafting and constitution checks.

If your feature specification has unresolved clarifications during implementation planning, the planning workflow will fail. The system requires all clarification placeholders in the technical context to be resolved before proceeding to Phase 1 contract and data model generation.

Implementation planning supports custom extension hooks by reading .specify/extensions.yml. It runs before_plan and after_plan hooks while distinguishing between optional and mandatory behavior, safely skipping execution if the YAML file is invalid or missing.

To run a constitution check before generating data models and contracts, the planning workflow reads constitution.md during initialization and re-checks it after design completion. Gate violations will halt the artifact generation process.

Executing the spec-kit plan template workflow requires a repository containing the .specify directory structure. You must provide a FEATURE_SPEC file, a constitution.md file, and run the setup-plan and agent-context update scripts to establish technical context.

Research consolidation occurs during Phase 0 of the implementation planning workflow. It gathers technical context from the feature specification, fills clarification placeholders, and prepares the foundational knowledge needed to generate data models, contracts, and quickstart artifacts.