speckit-plan

Implementation planning from a feature spec uses a gated workflow to generate research and design artifacts. It converts the spec into research.md, data-model.md, contracts, and quickstart.md by resolving unknowns and validating against the constitution before proceeding to design steps.

A gated workflow for implementation planning enforces sequential progression by requiring research completion before design steps. It converts NEEDS CLARIFICATION items into mandatory research tasks, ensuring all unknowns are resolved and constitution checks pass before generating data models and contracts.

Extracting a data model and contracts from a feature spec involves running the phased planning workflow. During Phase 1, the workflow generates data-model.md and scaffolds the contracts directory after successfully completing Phase 0 research and resolving all specification unknowns.

You can use custom extension hooks during spec-to-design planning by declaring before_plan and after_plan hooks in the .specify/extensions.yml file. The workflow runs these optional or mandatory hooks without evaluating their internal conditions during execution.

You need a spec-kit repository to run the planning workflow because the process requires loading FEATURE_SPEC and constitution context. It also requires executing the setup-plan PowerShell script at the repo root to correctly generate the design artifacts.

Implementation planning fails on unjustified gate violations to enforce design integrity and prevent missing requirements. The workflow intentionally blocks progression to design phases if mandatory research tasks are incomplete or constitution checks are violated without valid justification.