speckit-plan

Generate implementation plans and design artifacts from feature specifications.

2|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/guestgraph/engine --skill speckit-plan-guestgraph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/guestgraph/engine/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/guestgraph/engine --skill speckit-plan-guestgraph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires research, data modeling, and contract design work that is easy to skip or do inconsistently. This Skill automates that planning workflow so every feature gets structured design artifacts before coding begins. ## Core Features & Use Cases - Plan Workflow Execution: Runs the setup script, loads the feature spec and project constitution, and fills the plan template including Technical Context and Constitution Check gates. - Research and Design Artifacts: Generates research.md to resolve unknowns, then produces data-model.md, API contracts, and quickstart.md validation guides. - Extension Hooks: Dispatches optional and mandatory before/after plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec with spec-kit, invoke this Skill to produce a complete implementation plan with resolved technical decisions, entity models, and interface contracts ready for task breakdown. ## 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 create 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 into research.md, and generates data-model.md, contracts, and quickstart.md.

What artifacts does the spec-kit planning workflow generate?▼

The workflow generates research.md with resolved technical decisions, 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/bash/setup-plan.sh, memory/constitution.md, and the feature spec on the current branch. Without this structure the setup step cannot locate the required files.

What happens when Technical Context has unresolved unknowns?▼

Unknowns are marked as NEEDS CLARIFICATION and converted into research tasks during Phase 0. Each is resolved with a decision, rationale, and alternatives in research.md before Phase 1 design proceeds.

How do extension hooks work in the planning workflow?▼

Hooks are read from .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Mandatory hooks are executed automatically and the workflow waits for them; optional hooks are displayed with their command for manual execution.