speckit-plan

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires structured research, data modeling, and contract definition, which is time-consuming and inconsistent when done manually. ## Core Features & Use Cases - Automated Plan Setup: Runs the spec-kit setup script to resolve feature spec, plan file, specs directory, and branch context. - Phased Design Workflow: Executes Phase 0 research to resolve unknowns into research.md, then Phase 1 to produce data-model.md, contracts, and quickstart.md. - Constitution & Gate Checks: Validates the plan against the project constitution and errors on unjustified violations or unresolved clarifications. - 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, run this skill to automatically generate the research, data model, API contracts, and quickstart validation guide for the feature branch. ## Quick Start Run the speckit-plan skill with your planning notes 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 generate an implementation plan from a feature spec?▼

Run the speckit-plan skill inside a spec-kit project. It executes setup-plan.sh to load the feature spec and plan template, then fills the Technical Context, runs research, and produces design artifacts like data-model.md and contracts.

What artifacts does the spec-kit plan workflow produce?▼

The workflow produces research.md in Phase 0, resolving all NEEDS CLARIFICATION items, and data-model.md, a contracts directory, and quickstart.md in Phase 1. It also reports the branch and implementation plan path on completion.

Does speckit-plan require a specific project structure?▼

Yes, it requires a spec-kit project structure with a .specify directory containing scripts, memory/constitution.md, and templates. Without this structure the setup script and constitution checks cannot run.

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

Extension hooks are commands defined 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 fail with gate errors?▼

The workflow errors when constitution check violations are unjustified or when NEEDS CLARIFICATION items remain unresolved after Phase 0 research. Resolve the unknowns in research.md or justify violations in the plan to proceed.