speckit-plan

Implementation planning automation generates design artifacts by loading an IMPL_PLAN template and executing a phase-driven workflow to produce research.md, data-model.md, contracts, and quickstart documentation. This approach enforces hook handling and error gating for auditable agent workflows.

A spec-kit style project is a repository structure containing a .specify directory and IMPL_PLAN templates. It handles planning workflows by applying phase-driven execution and hook evaluation to generate structured design artifacts while maintaining strict input parsing and context updates.

Automate implementation planning by running a workflow that enforces strict input parsing and error gating against a plan template. This safely evaluates pre- and post-plan extension hooks, updating plan references and context after each design phase to ensure repeatable results.

Yes, a .specify directory is required to generate project implementation artifacts. The planning workflow specifically targets spec-kit style projects, relying on this directory structure to locate IMPL_PLAN templates and enforce phase-driven outputs for artifact generation.

Limitations of phase-driven design doc generation include strict input parsing requirements and error gating that halt execution upon invalid contexts. It relies entirely on the presence of a .specify directory and IMPL_PLAN templates to generate research.md and data-model.md files successfully.