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/dperussina/function2agent --skill speckit-plan-dperussina
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/dperussina/function2agent/tree/main/.cursor/skills/speckit-plan
Command: npx skills add https://github.com/dperussina/function2agent --skill speckit-plan-dperussina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, modeling data, and defining contracts, which is slow and inconsistent when done manually. This Skill automates that planning workflow inside a spec-kit project. ## 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. - Research and Design Artifacts: Generates research.md to resolve open questions, then produces data-model.md, contracts/, and quickstart.md during Phase 0 and Phase 1. - 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 repository, invoke this Skill to produce a complete plan with resolved clarifications, a data model, interface contracts, and a validation quickstart guide. ## Quick Start Run the speckit-plan skill with your feature details to generate the implementation plan and design artifacts for the current spec-kit branch.

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 inside a spec-kit project. It executes .specify/scripts/bash/setup-plan.sh, loads the feature spec and constitution, then fills the plan template and generates research.md, data-model.md, contracts, and quickstart.md.

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

The workflow produces research.md resolving all NEEDS CLARIFICATION items in Phase 0, then data-model.md, interface contracts under contracts/, and quickstart.md in Phase 1, alongside the filled implementation plan file.

Does speckit-plan require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing the setup-plan.sh script, memory/constitution.md, and the feature spec. Without this structure the setup step cannot locate the plan paths.

How do extension hooks work in the planning workflow?▼

If .specify/extensions.yml defines hooks under hooks.before_plan or hooks.after_plan, enabled hooks are executed before or after planning. Hooks with a non-empty condition are skipped and left to the HookExecutor, and disabled hooks are filtered out.

What happens when the constitution check fails during planning?▼

Gate violations in the Constitution Check section cause an ERROR unless they are justified in the plan. The check is evaluated once after loading context and again after Phase 1 design is complete.