speckit-plan

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

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-plan-acarmonag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/acarmonag/fullstack-devops-agent-aws-terraform/tree/main/codebase/rdicidr-0.1.0/.claude/skills/speckit-plan
Command: npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-plan-acarmonag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires structured research, data modeling, and contract definition, 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 Technical Context and Constitution Check sections in the plan template. - Design Artifact Generation: Produces research.md, data-model.md, contracts/, and quickstart.md through Phase 0 (research) and Phase 1 (design) stages. - 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 with spec-kit, invoke this skill to resolve all NEEDS CLARIFICATION items, generate a data model, and produce interface contracts ready for task breakdown. ## Quick Start Run the speckit-plan skill with optional planning guidance 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?▼

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 in Phase 0, resolving all NEEDS CLARIFICATION items, and data-model.md, a contracts directory, and quickstart.md in Phase 1. It also re-evaluates the Constitution Check after design.

Does speckit-plan require a specific project structure?▼

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

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 before continuing, while optional hooks are presented for manual invocation. Hooks with enabled set to false are skipped.

What happens when Technical Context contains unknowns?▼

Unknowns are marked as NEEDS CLARIFICATION and converted into research tasks in Phase 0. Each unknown is researched and consolidated into research.md with a decision, rationale, and alternatives considered before design proceeds.