speckit-plan

Generates implementation plans, research notes, and design contracts from feature specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires coordinating research, data modeling, and contract design, which is error-prone when done ad hoc. This Skill automates the spec-kit planning workflow so design artifacts are produced consistently. ## Core Features & Use Cases - Plan Workflow Execution: Runs the setup script, loads the feature spec and project constitution, and fills the implementation plan template with technical context and constitution checks. - Research and Design Phases: Resolves NEEDS CLARIFICATION items into research.md, then generates data-model.md, interface contracts, and quickstart.md. - Extension Hooks and Timing: Executes optional or mandatory before/after plan hooks from .specify/extensions.yml and records step and substep timing via the companion write-context script. - Use Case: After writing a feature spec with spec-kit, invoke this Skill to produce a complete plan directory with research findings, entity models, and API contracts ready for task breakdown. ## Quick Start Run the speckit plan workflow on my current feature branch to generate the implementation plan, research notes, and design contracts from the 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?▼

Run the speckit plan workflow, which executes .specify/scripts/bash/setup-plan.sh to locate the feature spec and plan template, then fills technical context, constitution checks, research, and design phases automatically.

What artifacts does the spec-kit planning phase produce?▼

The planning phase produces research.md resolving all open questions, data-model.md with entities and validation rules, interface contracts under /contracts/, quickstart.md, and an updated agent context file pointing to the plan.

Does speckit-plan require a specific project structure?▼

Yes, it requires a spec-kit project with a .specify directory containing scripts, memory/constitution.md, and feature specs. Without this structure the setup script and template loading steps cannot run.

How do extension hooks work in the planning workflow?▼

Hooks are defined in .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Enabled hooks with no condition are executed or offered as slash commands, with dots in command names converted to hyphens.

Why should I not edit .spec-context.json manually?▼

Hand-editing corrupts the timing file, for example by duplicating the status key. All timing updates must go through the write-context.py script, which stamps the real clock, writes atomically, and is idempotent.