speckit-plan

To generate an implementation plan from a feature specification, you run a planning workflow that loads your feature spec and project constitution to produce design artifacts. It resolves unknowns through research and drafts entity models and contracts for execution.

Drafting data models and contracts from a spec-kit repository involves running an automated planning phase that reads your feature spec. It generates structured data-model.md files and contract definitions directly from the extracted project requirements.

Yes, the planning workflow updates agent context automatically after generating artifacts. It modifies the AGENTS.md file by inserting references between specific markers so subsequent agent runs point to the newly created plan file.

You can run custom extension hooks before and after implementation planning by registering them in your extensions configuration file. The workflow executes pre-plan hooks to enforce steps before starting and post-plan hooks after reporting the generated artifacts.

Research generation works by analyzing your feature specification and project constitution to resolve unknowns before drafting design artifacts. It produces a structured research.md file that informs the subsequent data model and contract generation phases.

From the Specify implementation planning phase, you should expect outputs including research.md, data-model.md, quickstart.md, and a contracts directory. These artifacts fulfill the project-structure requirements and stop execution after Phase 2.