speckit-plan

To generate an implementation plan for a Spec-Kit feature request, provide your requirements to trigger the planning workflow, which produces research notes, data models, contracts, and quickstart guidance. The plan orchestrates project readiness checks and constitution constraints before outputting design artifacts.

Planning software changes in a spec-kit repository requires a valid SKILL.md workflow, .specify configuration, and passing project readiness checks for structure and constitution constraints. The setup ensures the environment supports generating research, data models, and contract artifacts.

The spec-kit planning workflow handles data models and contracts by generating them as needed from your initial feature requirements. It processes the request through design artifact phases to ensure the contracts and data models align with the project's constitution checks.

No, you cannot use speckit-plan without a .specify configuration and a valid SKILL.md workflow. The skill applies specifically to repositories following the spec-kit project structure and relies on these files to verify readiness and execute the planning sequence.

The design artifacts produced when creating an implementation plan include research notes, data models, contracts, quickstart guidance, and agent context updates. These artifacts are generated sequentially to support confident implementation of the requested software changes.