speckit-plan

Name: speckit-plan
Availability: InStock
Author: mustafaelshahhat-art

Generate research and design artifacts from feature specifications with gated phases.

Updated Aug 27, 2026

Search Tags:#implementation planning #workflow orchestration #data model #spec-kit #contracts #extension hooks #research generation

Ready to run

npx skills add https://github.com/mustafaelshahhat-art/Dr_Mirror --skill speckit-plan-mustafaelshahhat-art

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/mustafaelshahhat-art/Dr_Mirror/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/mustafaelshahhat-art/Dr_Mirror --skill speckit-plan-mustafaelshahhat-art

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-plan turns an input feature spec into an implementation plan with concrete design artifacts, reducing guesswork and missing requirements.

Core Features & Use Cases

Generates phased planning artifacts: produces research.md, data-model.md, contracts/, and quickstart.md across Phase 0 and Phase 1.
Resolves unknowns using gated workflows: converts NEEDS CLARIFICATION items into research tasks and requires research completion before design steps proceed.
Supports extension hooks: runs optional or mandatory before_plan and after_plan hooks declared in .specify/extensions.yml without evaluating hook conditions.

Quick Start

Run the plan workflow at the repo root so it creates research.md and subsequent design outputs using the plan template and any configured extension hooks.

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 specification?▼

Implementation planning from a feature spec uses a gated workflow to generate research and design artifacts. It converts the spec into research.md, data-model.md, contracts, and quickstart.md by resolving unknowns and validating against the constitution before proceeding to design steps.

What is a gated workflow for implementation planning?▼

A gated workflow for implementation planning enforces sequential progression by requiring research completion before design steps. It converts NEEDS CLARIFICATION items into mandatory research tasks, ensuring all unknowns are resolved and constitution checks pass before generating data models and contracts.

How do I extract a data model and contracts from a feature spec?▼

Extracting a data model and contracts from a feature spec involves running the phased planning workflow. During Phase 1, the workflow generates data-model.md and scaffolds the contracts directory after successfully completing Phase 0 research and resolving all specification unknowns.

Can I use custom extension hooks during spec-to-design planning?▼

You can use custom extension hooks during spec-to-design planning by declaring before_plan and after_plan hooks in the .specify/extensions.yml file. The workflow runs these optional or mandatory hooks without evaluating their internal conditions during execution.

Do I need a spec-kit repository to run the planning workflow?▼

You need a spec-kit repository to run the planning workflow because the process requires loading FEATURE_SPEC and constitution context. It also requires executing the setup-plan PowerShell script at the repo root to correctly generate the design artifacts.

Why does implementation planning fail on unjustified gate violations?▼

Implementation planning fails on unjustified gate violations to enforce design integrity and prevent missing requirements. The workflow intentionally blocks progression to design phases if mandatory research tasks are incomplete or constitution checks are violated without valid justification.