speckit-plan

Execute plan templates to generate design artifacts for spec-kit projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and generating design artifacts from templates can be error-prone and time-consuming. This Skill automates the end-to-end implementation planning workflow, ensuring consistent outputs such as research.md, data-model.md, contracts, quickstart.md, and an updated AGENTS.md, by enforcing a predefined plan and extension-hooks process.

Core Features & Use Cases

  • Executes the implementation planning workflow using the plan template to generate artifacts such as research.md, data-model.md, contracts/, quickstart.md, and updated agent context.
  • Integrates with a spec-kit style project structure using .specify/ directories and extension hooks defined in .specify/extensions.yml.
  • Supports pre- and post-execution checks, gates, and phase-based artifact generation for repeatable design processes.

Quick Start

Run speckit-plan on a project to execute the plan template and generate design artifacts across the planned phases.

Frequently Asked Questions about speckit-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate implementation planning to generate design artifacts like data models and contracts?

Automating implementation planning requires validating and executing a plan template to produce design artifacts. This workflow enforces a predefined process to generate consistent outputs like research.md, data-model.md, contracts, and quickstart.md.

What is a spec-kit project structure and when do I need extension hooks for planning?

A spec-kit project structure uses .specify/ directories and memory constitution to manage implementation plans. You need extension hooks defined in .specify/extensions.yml when executing pre- and post-execution checks for phase-based artifact generation.

Does this planning workflow require a specific directory structure to run?

Yes, this planning workflow requires a compliant SPEC-KIT structure to run. It relies on a project setup with .specify/ memory constitution, IMPL_PLAN templates, and extension hooks managed via .specify/extensions.yml.

How do I execute the plan template and generate artifacts across planned phases?

To execute the plan template, run the workflow on a compliant spec-kit project. It applies phase-based artifact generation, running pre- and post-execution gates to safely produce research.md, data-model.md, and updated AGENTS.md.

What are the limitations of using plan templates for design artifact generation?

A key limitation is the strict requirement for a compliant SPEC-KIT structure. The workflow cannot validate or execute properly without the .specify/ directory, IMPL_PLAN templates, and safe execution of pre/post hooks.