speckit-plan

Generate implementation plans and design artifacts from feature specifications.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/linhnguyen125/ClaudeCodeWithSpecKit --skill speckit-plan-linhnguyen125
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/linhnguyen125/ClaudeCodeWithSpecKit/tree/main/.claude/skills/speckit-plan-vi
Command: npx skills add https://github.com/linhnguyen125/ClaudeCodeWithSpecKit --skill speckit-plan-linhnguyen125

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a feature specification into a coordinated implementation plan and set of design artifacts for projects using the spec-kit structure, removing manual orchestration and ensuring gated checks and artifact consistency.

Core Features & Use Cases

  • Multi-agent orchestration: coordinates a plan-lead with fe-planner and be-planner to run parallel research, design, and planning phases.
  • Phase-based workflow: executes Setup, Phase 0 (research), Phase 1 (design/contracts), Phase 2 (implementation planning), and Synthesis to produce IMPL_PLAN.md and related artifacts.
  • Project integration & hooks: runs setup scripts, loads FEATURE_SPEC and constitution, respects pre/post extension hooks and constitution gates, and reports branch and artifact outputs.
  • Use Case: Generate FE and BE implementation plans and IPC/API contracts for a FlowPilot monorepo feature spec.

Quick Start

Invoke the speckit-plan skill to generate an IMPL_PLAN.md and related artifacts from the feature specification in .specify/ using the plan template.

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 specification in a monorepo?

Generating an implementation plan from a feature specification involves loading the spec, running phased research and design workflows, and outputting an IMPL_PLAN.md along with related design artifacts.

What is multi-agent planning for frontend and backend feature development?

Multi-agent planning coordinates a plan-lead with separate frontend and backend planners to execute parallel research, design, and implementation phases, producing unified project artifacts.

Does spec-kit structured planning support constitution gates and extension hooks?

Spec-kit structured planning enforces constitution gates and respects pre/post extension hooks by loading the project constitution and applying gated checks throughout the phased workflow.

How do I coordinate FE and BE implementation plans and API contracts for a feature spec?

Coordinating FE and BE implementation plans requires a phased workflow where separate planners run parallel design and planning tasks to produce IPC/API contracts and a unified IMPL_PLAN.md.

Can I use multi-agent implementation planning for FlowPilot monorepo projects?

Multi-agent implementation planning applies to FlowPilot monorepo projects because the workflow is specifically designed to handle monorepo structures with spec-kit configurations.