speckit-plan

Generates implementation plans and design artifacts from feature specifications using spec-kit templates.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/charlesguse/wing-commander --skill speckit-plan-charlesguse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/charlesguse/wing-commander/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/charlesguse/wing-commander --skill speckit-plan-charlesguse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved feature specification into a concrete technical plan requires resolving unknowns, modeling data, and defining contracts, which is slow and inconsistent when done manually. ## Core Features & Use Cases - Plan Workflow Execution: Runs the spec-kit planning workflow via setup-plan.sh, filling Technical Context and Constitution Check sections from the project constitution. - Research & Design Artifacts: Generates research.md to resolve NEEDS CLARIFICATION items, then produces data-model.md, contracts/, and quickstart.md. - Extension Hooks: Executes optional and mandatory before_plan and after_plan hooks declared in .specify/extensions.yml. - Use Case: After a spec PR is merged, invoke this skill to produce a reviewed implementation plan with resolved technical decisions and interface contracts for a new feature. ## Quick Start Run the speckit-plan skill on the current feature branch to generate the implementation plan and design artifacts from the approved spec.

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 skill on the feature branch. It executes setup-plan.sh, loads the feature spec and constitution, fills the plan template, and produces research.md, data-model.md, contracts, and quickstart.md.

What artifacts does the spec-kit planning phase produce?▼

Phase 0 produces research.md resolving all NEEDS CLARIFICATION items. Phase 1 produces data-model.md with entities and validation rules, a contracts directory for external interfaces, and quickstart.md with validation scenarios.

Does speckit-plan require a specific project structure?▼

Yes, it requires a spec-kit project structure with a .specify directory containing scripts, memory/constitution.md, and templates. It must run from the repository root on a feature branch.

What happens when the constitution check fails during planning?▼

The workflow raises an ERROR on gate failures or unjustified constitution violations. Violations must be justified in the plan, and unresolved clarifications also block completion.

How do extension hooks work in the planning workflow?▼

Hooks declared under hooks.before_plan and hooks.after_plan in .specify/extensions.yml are executed before and after planning. Mandatory hooks run automatically; optional hooks are presented for manual invocation.