speckit-plan

Generates implementation plans and design artifacts from feature specifications.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill speckit-plan-karentenorio963
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/KarenTenorio963/curso-mcp-karentenorio/tree/main/entregas/s4/mi-proyecto-speckit/.agents/skills/speckit-plan
Command: npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill speckit-plan-karentenorio963

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 when done manually. ## Core Features & Use Cases - Plan Workflow Execution: Runs the spec-kit planning workflow via setup-plan.ps1, filling the Technical Context and Constitution Check sections of the plan template. - Research and 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 defined in .specify/extensions.yml. - Use Case: After writing a feature spec in a spec-kit project, run this Skill to produce a complete implementation plan with research decisions, entity models, API contracts, and a validation quickstart guide. ## Quick Start Run the speckit-plan skill to generate the 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.ps1 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 with decisions and rationales, 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 with a .specify/ directory containing scripts/powershell/setup-plan.ps1 and memory/constitution.md. It runs on a feature branch with an existing FEATURE_SPEC file.

What happens when Technical Context has unresolved items?▼

Items marked NEEDS CLARIFICATION become research tasks in Phase 0. The workflow dispatches research for each unknown and consolidates decisions, rationales, and alternatives in research.md before design begins.

How do extension hooks work in the planning workflow?▼

If .specify/extensions.yml defines hooks under before_plan or after_plan, enabled hooks without conditions are executed. Mandatory hooks run automatically and block progress; optional hooks are presented for manual execution.