speckit-plan

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

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-plan-secrakib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/secrakib/rag-eval-project/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-plan-secrakib

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 - Automated Plan Setup: Runs the spec-kit setup script to locate the feature spec, plan file, and branch context. - Research Generation: Resolves all NEEDS CLARIFICATION items in the Technical Context and consolidates findings into research.md. - Design Artifact Generation: Produces data-model.md, interface contracts, and quickstart.md following the plan template phases. - Extension Hooks: Executes optional and mandatory before/after plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec with spec-kit, run this Skill to automatically produce the research, data model, API contracts, and quickstart validation guide for the feature branch. ## 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 in a spec-kit project. It executes setup_plan.py to locate the feature spec and plan file, then fills the 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, 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/python/setup_plan.py, memory/constitution.md, and the plan template. Without this structure the setup step cannot locate the feature spec and plan files.

What are extension hooks in the spec-kit plan workflow?▼

Extension hooks are commands registered under hooks.before_plan and hooks.after_plan in .specify/extensions.yml. Mandatory hooks are executed automatically before or after planning, while optional hooks are only suggested to the user.

Why does the plan workflow stop with a constitution check error?▼

The workflow evaluates constitution gates before and after design. If a design violates constitution principles without documented justification, the workflow errors out instead of continuing, enforcing project governance rules.