speckit-plan

Automating planning to generate design artifacts involves applying a structured plan template to produce files like research.md, data-model.md, and contracts. This reduces manual overhead and errors by aligning project planning with a repeatable, deterministic workflow.

Artifact generation within a spec-kit project structure works by operating within a .specify/ directory and applying plan templates. It enforces gates and constitution checks to ensure plan validity before execution, producing phased outputs like research.md and quickstart documentation.

Pre-plan and post-plan extension hooks are supported within a .specify/ project structure for deterministic planning. These hooks allow you to customize the workflow before and after the template is applied, ensuring the generated design artifacts meet specific project requirements.

The best way to ensure plan validity before execution is by enforcing gates and constitution checks during the planning workflow. These checks validate the plan against predefined rules before generating artifacts like data-model.md and contracts.

A .specify/ directory is required to run the speckit-plan workflow. The skill operates within this specific project structure to support extension hooks, enforce gates, and generate design artifacts like research.md and data-model.md.

Updating agent context after generating project planning artifacts is handled automatically by the workflow. After applying the plan template and producing outputs like contracts and quickstart documentation, the context is updated to reflect the latest plan while reporting results to the user.