speckit-plan

To generate an implementation plan from a feature specification, use a structured workflow that reads your spec and constitution, runs setup scripts, and produces gated design artifacts like research and data model files. This ensures your planning process is structured and validated.

The planning workflow handles clarification by resolving needs during an initial Phase 0 generation step. It enforces strict gate rules and immediately stops the process, reporting errors, if any validation violations occur during artifact generation.

Yes, you need a .specify directory to run the spec-kit planning workflow. This directory stores your setup scripts, constitution context, extension hooks, and template files required to execute the phased artifact generation successfully.

The two-phase implementation planning process first produces a research document, followed by a data model file, optional contracts, and a quickstart guide. These artifacts provide the structured design foundation needed before coding begins.

Yes, you can run custom extension hooks before generating implementation plans. The workflow detects optional and mandatory pre-hooks from your extensions configuration file and prepares the execution flow accordingly before starting the planning phases.

Implementation plan generation stops with a gate failure error because the workflow actively enforces predefined guardrails and validation rules. It halts immediately upon detecting violations to prevent generating incomplete or invalid design artifacts.