speckit-plan

To generate an implementation plan from a feature spec, the workflow resolves NEEDS CLARIFICATION items via targeted research, then produces data-model.md, contract docs, and quickstart.md artifacts. It enforces gate checks and updates agent context markers in CLAUDE.md.

The best way to resolve unknowns in a feature spec is converting NEEDS CLARIFICATION items into targeted research tasks. The workflow consolidates findings into research.md to eliminate ambiguity before producing architecture contracts and data models.

Yes, spec automation requires a .specify directory structure. You must run the setup-plan PowerShell script, load constitution memory, and follow the IMPL_PLAN template phases to successfully generate the planning artifacts.

Yes, you can use custom extension hooks during implementation planning by defining optional and mandatory hooks in .specify/extensions.yml. The workflow detects before_plan and after_plan hooks and prints appropriate execution directives.

Creating architecture contracts from a feature spec produces research.md, data-model.md, contract documents under the contracts/ directory, and quickstart.md. It also updates agent context markers within CLAUDE.md.

The workflow updates agent context by modifying markers in CLAUDE.md after generating design artifacts. This ensures the agent operates with the latest data-model and contract definitions during subsequent implementation phases.