speckit-plan

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

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-plan-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-plan-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, designing data models, and defining contracts, which is time-consuming and error-prone when done manually. ## Core Features & Use Cases - Plan Workflow Execution: Runs the spec-kit planning workflow via setup-plan.sh, filling the Technical Context and Constitution Check sections of the plan template. - Research & Design Artifacts: Generates research.md, data-model.md, contracts/, and quickstart.md by resolving NEEDS CLARIFICATION items and extracting entities from the feature spec. - Extension Hooks: Dispatches 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 produce a complete implementation plan with resolved research questions, a data model, API contracts, and a validation quickstart guide. ## Quick Start Run the speckit-plan skill to generate an implementation plan and design artifacts for the current feature 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 workflow, which executes setup-plan.sh to locate the feature spec and plan template, then fills the Technical Context, resolves unknowns in research.md, and produces data-model.md, contracts, and quickstart.md.

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

The workflow produces research.md in Phase 0, then data-model.md, a contracts/ directory, and quickstart.md in Phase 1. It also re-evaluates the Constitution Check after design and reports the branch and plan path.

Does speckit-plan require a specific project structure?▼

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

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 are executed automatically and the workflow waits for them, while optional hooks are only suggested with their command and prompt.

What happens when the plan has unresolved NEEDS CLARIFICATION items?▼

Each NEEDS CLARIFICATION item in the Technical Context becomes a research task in Phase 0. The workflow dispatches research for each unknown and consolidates decisions, rationale, and alternatives into research.md before design begins.