speckit-plan

Execute speckit implementation planning workflows with gate-checked phases and artifact generation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-plan helps you reliably turn a feature spec into an implementation outline and phase-based plan, including resolving unknowns and updating agent context in the correct project structure.

Core Features & Use Cases

  • Pre-Execution Extension Hooks: Reads .specify/extensions.yml and runs before_plan hooks (with optional vs automatic handling) when present and enabled.
  • Deterministic Plan Orchestration: Executes the repository plan setup script, loads the feature spec and constitution, then follows the defined research and design/contract phases.
  • Artifact Generation & Validation Gates: Produces research.md, data-model.md, contract stubs, and quickstart.md while enforcing “NEEDS CLARIFICATION” resolution and failing on gate violations.
  • Post-Execution Extension Hooks: Optionally runs after_plan hooks and reports the created plan path and artifacts.

Quick Start

Ask an AI to run speckit-plan in your spec-kit repository by planning Phase 0 and Phase 1 from the current feature spec and constitution, resolving all NEEDS CLARIFICATION items and producing research.md and implementation 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 roadmap from a feature specification?

To generate an implementation roadmap, the speckit-plan workflow orchestrates setup, context loading, and research phases to produce structured plan artifacts. It parses feature specs and updates agent context deterministically.

What is the best way to draft contracts and data models from a spec-kit project?

Drafting contracts and data models from a spec-kit project involves following the defined design phase to generate data-model.md and contract stubs. This process enforces validation gates to ensure all unknowns are resolved.

How does deterministic planning handle unresolved items in a feature specification?

Deterministic planning handles unresolved items by enforcing 'NEEDS CLARIFICATION' resolution gates during artifact generation. The workflow fails on gate violations, ensuring all ambiguities are resolved before producing the final plan.

Can I run custom extension hooks before and after generating an implementation plan?

Yes, you can run custom extension hooks by defining them in .specify/extensions.yml. The workflow supports optional and automatic before_plan and after_plan hooks to execute custom logic and report created plan paths.

Do I need a specific directory structure to use spec-kit implementation planning?

Yes, spec-kit implementation planning requires the .specify directory structure. The workflow reads .specify/memory/constitution.md and executes the repository plan setup script to ensure deterministic, gate-checked planning.

Why does implementation plan generation fail during the research phase?

Implementation plan generation fails during the research phase when validation gates detect unresolved 'NEEDS CLARIFICATION' items or missing required artifacts like research.md. The workflow enforces these gates to prevent incomplete plans.