speckit-plan

To generate design artifacts from a plan template, execute a planning workflow that validates project structure and outputs files including data-model.md, contracts, and quickstart.md. This process enforces pre-execution checks and gates during artifact generation.

A plan-driven implementation workflow streamlines software design by executing a plan template to produce actionable artifacts. It covers steps from setup to artifact generation, enforcing gates and extension hooks to output research.md, data models, and contracts.

Yes, the planning workflow requires a project structure that includes a .specify directory and plan templates. This directory is necessary for the workflow to execute pre-execution checks, apply extension hooks, and generate the required design artifacts.

Yes, you can use extension hooks to customize the design artifact generation process. The planning workflow enforces pre-execution checks, gates, and extension hooks, allowing you to update agent context and output artifacts like research.md and quickstart.md.

The best way to enforce pre-execution checks during implementation planning is by using a plan template workflow that validates project structure and applies gates and extension hooks. This ensures proper setup before generating artifacts like contracts and data models.

The planning workflow updates agent context after generating artifacts to ensure downstream processes have the latest design information. It outputs artifacts like research.md, data-model.md, and contracts, then updates the context as part of the final planning steps.