speckit-plan

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

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

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 interface contracts, which is time-consuming when done manually. ## Core Features & Use Cases - Planning Workflow Execution: Runs the spec-kit plan workflow via setup-plan.sh, filling Technical Context and Constitution Check sections in the plan template. - 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 project, invoke this Skill to produce a complete implementation plan with resolved technical decisions, entity models, and validation guides. ## Quick Start Run the speckit-plan skill to generate the implementation plan and design artifacts for the current feature branch in my spec-kit project.

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?▼

Invoke the speckit-plan skill in a spec-kit project. It runs setup-plan.sh to locate the feature spec and plan template, then fills 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 with resolved technical decisions, data-model.md with entities and validation rules, a contracts directory for external interfaces, and quickstart.md with runnable validation scenarios.

Does speckit-plan require a specific project structure?▼

Yes, it requires a spec-kit project structure with a .specify/ directory containing scripts like setup-plan.sh and a memory/constitution.md file. Without this structure the planning workflow cannot run.

What happens when Technical Context has unresolved questions?▼

Unknowns are marked as NEEDS CLARIFICATION and converted into research tasks during Phase 0. Each unknown is investigated and consolidated into research.md with a decision, rationale, and alternatives considered.

Can I run custom hooks before or after the planning phase?▼

Yes, define hooks under hooks.before_plan or hooks.after_plan in .specify/extensions.yml. Mandatory hooks execute automatically, while optional hooks are presented as suggestions with their command and description.