speckit-plan

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

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill speckit-plan-desarrolloainia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/desarrolloainia/nuevo_circuito_mir/tree/main/backend/.agents/skills/speckit-plan
Command: npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill speckit-plan-desarrolloainia

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 - Planning Workflow Execution: Runs the spec-kit plan workflow to fill Technical Context, perform Constitution Checks, and evaluate design gates. - Design Artifact Generation: Produces research.md, data-model.md, contracts/, and quickstart.md from the feature spec. - Extension Hook Support: Executes optional and mandatory before/after plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec in a spec-kit project, invoke this Skill to resolve all NEEDS CLARIFICATION items and generate the full Phase 0 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 spec.

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.ps1 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 in Phase 0, resolving all NEEDS CLARIFICATION items, and data-model.md, a contracts/ directory, and quickstart.md in Phase 1. It also reports the branch and IMPL_PLAN path on completion.

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 template.

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 before continuing, while optional hooks are presented to the user with their command and prompt.

What happens when Technical Context has unresolved unknowns?▼

Each NEEDS CLARIFICATION item becomes a research task in Phase 0. The workflow dispatches research for unknowns, technology best practices, and integration patterns, then consolidates decisions, rationale, and alternatives in research.md.