speckit-plan

Generates implementation plans and design artifacts from feature specifications using the spec-kit plan template.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-plan-speeddesigns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/speeddesigns/cvusd-calendars/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-plan-speeddesigns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires structured research, data modeling, and contract definition, which is error-prone when done ad hoc. This Skill automates the spec-kit planning workflow so design artifacts are produced consistently. ## Core Features & Use Cases - Plan Workflow Execution: Runs the setup script, loads the feature spec and project constitution, and fills the implementation plan template with technical context and constitution checks. - Design Artifact Generation: Produces research.md, data-model.md, contracts/, and quickstart.md through Phase 0 research and Phase 1 design. - Extension Hook Support: Evaluates before_plan and after_plan hooks from .specify/extensions.yml and executes mandatory hooks automatically. - Use Case: After writing a feature spec in a spec-kit project, invoke this Skill to resolve open questions, define the data model, and generate a validated implementation plan ready for task breakdown. ## Quick Start Ask the agent to run the speckit plan workflow for the current feature branch to generate the implementation plan and design artifacts.

Frequently Asked Questions about speckit-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an implementation plan from a feature spec?

Run the speckit plan workflow, which executes setup-plan.ps1, loads the feature spec and constitution, then fills the plan template. It produces research.md, data-model.md, contracts, and quickstart.md as design artifacts.

What artifacts does the spec-kit plan workflow produce?

The workflow produces research.md resolving open questions in Phase 0, then data-model.md, interface contracts, and quickstart.md in Phase 1. It also re-evaluates the constitution check after design.

Does speckit-plan require a specific project structure?

Yes, it requires a spec-kit project with a .specify directory containing scripts, memory/constitution.md, and templates. Without this structure the setup script and plan template cannot be located.

How do extension hooks work in the plan workflow?

Hooks are declared in .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Mandatory hooks are executed automatically, optional hooks are only suggested, and hooks with conditions are skipped for the HookExecutor to evaluate.

What happens when the plan has unresolved clarifications?

Unknowns in the Technical Context are marked NEEDS CLARIFICATION and converted into research tasks in Phase 0. The workflow errors on unresolved clarifications or unjustified constitution gate failures.