speckit-plan

The speckit-plan skill is a core component of the Spec-Driven Development methodology, designed to bridge the gap between initial feature specifications and actionable technical implementation. It is intended for software engineers and technical leads who need to transform high-level requirements into structured, verifiable design strategies. By utilizing the predefined plan template, the agent automates the creation of essential design documents, ensuring consistency across development phases.

The skill operates by first establishing technical context, identifying gaps or ambiguities that require research, and validating the proposed plan against project-specific constitution principles. It streamlines the generation of technical documentation, including data models, API contracts, and research summaries, while maintaining tight integration with agent-specific context files. It is the critical step that follows feature specification and precedes task generation, effectively managing the 'how' of a feature's lifecycle.

• Automatically orchestrates the implementation planning workflow using local .specify/ templates.

• Generates comprehensive technical documentation including research.md, data-model.md, and structured /contracts/.

• Dispatches research agents to resolve 'NEEDS CLARIFICATION' items and investigate technology-specific best practices.

• Updates agent-specific context files to keep LLM memory aligned with the latest architecture and design decisions.

• Integrates validation gates to catch architectural or policy violations early in the planning phase.

• Requires a pre-existing feature specification file (specs/<feature>/spec.md) and initialized Spec Kit project.

• Operates by executing setup scripts from the .specify/ directory to parse paths and configure the workspace.

• Follows a structured phase-based approach: Phase 0 for research and gap analysis, Phase 1 for data modeling and contract generation.

• Generates OpenAPI or GraphQL schemas based on functional requirements derived from the spec.

• Essential for teams utilizing Spec-Driven Development to maintain architectural integrity and documentation-as-code.