speckit-plan

Implementation planning artifacts are produced by running a phased research-and-design workflow that generates research.md, data-model.md, contracts, and quickstart.md files. This workflow includes constitution re-checking after design and strict failure on unresolved clarifications.

Unresolved clarifications are handled by resolving NEEDS CLARIFICATION items via research tasks. The workflow enforces an ERROR state on gate failures or if any clarifications remain unresolved, ensuring no incomplete plans proceed.

Yes, you can run custom hooks before and after generating a design workflow by defining optional before_plan and after_plan hooks in your extensions configuration file. The workflow reads these hooks and runs or reports them according to their optional or mandatory behavior.

Spec-kit implementation planning generates research.md, data-model.md, contracts directories, and quickstart.md artifacts across Phase 0 and Phase 1. These artifacts are created after context loading and gate validation checks are successfully completed.

Yes, implementation planning supports JSON-based setup-plan parsing to orchestrate the workflow. It also satisfies requirements for optional extension hooks and enforces strict failure when gate validation encounters unresolved clarifications.