speckit-plan

Generates implementation plans and design artifacts from feature specifications using spec-kit templates.

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

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 - Planning Workflow Execution: Runs the spec-kit plan workflow via setup-plan.ps1, loading the feature spec and constitution to fill the implementation plan template. - Research and Design Artifacts: Generates research.md, data-model.md, contracts/, and quickstart.md through structured Phase 0 and Phase 1 steps. - Extension Hooks: Executes optional and mandatory before/after plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec in a spec-kit project, invoke this Skill to produce a complete plan with resolved clarifications, entity models, and validation guides. ## 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.ps1 to locate the feature spec and plan template, then fills Technical Context, resolves clarifications 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/powershell/setup-plan.ps1 and memory/constitution.md. Without this structure the planning workflow cannot run.

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 are executed automatically before continuing, while optional hooks are only suggested. Hooks with enabled set to false are skipped.

What happens when Technical Context has unresolved clarifications?

Each NEEDS CLARIFICATION entry becomes a research task in Phase 0. The findings are consolidated in research.md with decisions, rationale, and alternatives, and the workflow errors if clarifications remain unresolved.