speckit-plan

Automating implementation planning generates design artifacts by loading a plan template, populating technical context, and producing files like research.md, data-model.md, and contracts. This reduces manual planning time and promotes consistency across software development outputs.

Automating the planning workflow produces research.md, data-model.md, contracts, quickstart.md, and an updated AGENTS.md context file. These artifacts ensure traceability by recording the branch, plan path, and generated outputs for repeatable software design.

Yes, you can run custom scripts before and after the planning workflow using extension hooks configured in .specify/extensions.yml. These hooks support executable outputs and conditional execution rules to integrate seamlessly into the artifact generation process.

Automated planning handles traceability by recording the branch, IMPL_PLAN path, and generated artifacts during the workflow. It also re-evaluates constitution checks after design to ensure repeatable and consistent software development outputs.

Yes, you need an IMPL_PLAN template to automate design artifact generation. The workflow loads this plan template, populates the technical context from it, and produces the corresponding research, data model, and contract artifacts.

Extension hooks integrate with the automated planning workflow via .specify/extensions.yml, providing clear output for executable hooks and rules for enabled or conditional execution before and after the design artifacts are generated.