speckit-plan

To generate an implementation plan from a feature spec, use a planning workflow that processes the specification to produce research notes, data models, contracts, and quickstart guidance. This transforms feature requirements into structured, build-ready artifacts needed before coding starts.

Turning software specifications into data models and contracts requires executing a structured planning workflow. This process reads the feature spec, handles research unknowns, and outputs defined design artifacts and contracts to establish a clear technical foundation for implementation.

Spec-kit planning requires a valid .specify project structure within the repository. It relies on this specific directory setup to process extension hooks, run constitution checks, and update agent context properly during the implementation planning workflow.

You can use automated implementation planning to handle research unknowns before coding starts. The workflow analyzes the feature spec to generate research notes and design artifacts, reducing the manual effort needed to investigate technical uncertainties and define the data model.

Updating agent context when preparing implementation artifacts happens automatically during the spec-kit planning workflow. As the system processes the feature spec and generates design outputs like contracts and data models, it updates the project's agent context to reflect the new planning state.