speckit-plan

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

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-plan-andyrace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/AndyRace/heart-rate-graph/tree/main/.github/skills/speckit-plan
Command: npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-plan-andyrace

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 - Plan Workflow Execution: Runs the spec-kit planning workflow via setup-plan.ps1, filling Technical Context and Constitution Check sections in the plan template. - Research & Design Artifacts: Generates research.md in Phase 0 to resolve all NEEDS CLARIFICATION items, then produces data-model.md, contracts/, and quickstart.md in Phase 1. - Extension Hooks: 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 produce a complete design package including resolved research decisions, entity models, API contracts, and a validation quickstart guide. ## Quick Start Ask the agent to run the speckit plan workflow for the current feature branch to generate the implementation plan and design artifacts.

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 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 plan workflow produce?

The workflow produces research.md with resolved clarifications in Phase 0, then data-model.md, interface contracts under /contracts/, and quickstart.md in Phase 1. It also updates the implementation plan file with Technical Context and Constitution Check sections.

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

How do extension hooks work in the plan workflow?

Hooks are defined in .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Mandatory hooks (optional: false) are executed automatically, while optional hooks are presented to the user with their command and prompt.

What happens when Technical Context has unresolved unknowns?

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