speckit-plan

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, defining data models, and drafting 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.ps1, filling Technical Context and Constitution Check sections in the plan template. - Design Artifact Generation: Produces research.md, data-model.md, contracts/, and quickstart.md by resolving NEEDS CLARIFICATION items and extracting entities from the feature spec. - Extension Hook Support: Executes optional and mandatory before_plan and after_plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec in a spec-kit project, invoke this Skill to automatically generate the full Phase 0 research and Phase 1 design artifacts for the feature branch. ## Quick Start Run the speckit-plan skill to generate the implementation plan and design artifacts for my current feature specification.

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 in a spec-kit project. It executes setup-plan.ps1 to locate the feature spec and plan template, then fills Technical Context, resolves NEEDS CLARIFICATION items, and produces research.md, data-model.md, contracts, and quickstart.md.

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

The workflow produces research.md in Phase 0 with decisions, rationales, and alternatives, plus data-model.md, a contracts directory, 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/powershell/setup-plan.ps1 and memory/constitution.md. Without this structure the setup step cannot locate the feature spec and plan paths.

How do extension hooks work in the planning workflow?▼

Hooks are defined in .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Mandatory hooks (optional: false) are executed automatically, while optional hooks are presented for manual invocation. Hooks with a condition field are skipped.

What happens when Technical Context has unresolved unknowns?▼

Items marked NEEDS CLARIFICATION become research tasks in Phase 0. The workflow dispatches research for each unknown and consolidates findings in research.md before proceeding to Phase 1 design.