speckit-plan

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

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-plan-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.grok/skills/speckit-plan
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-plan-tjsasakifln

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 slow and inconsistent when done ad hoc. This Skill automates the spec-kit planning workflow so design artifacts are produced consistently from a feature spec. ## Core Features & Use Cases - Plan Setup and Context Loading: Runs the setup-plan script, parses feature spec paths, and loads the project constitution for gate evaluation. - Phase 0 Research: Resolves all NEEDS CLARIFICATION items and consolidates decisions, rationale, and alternatives into research.md. - Phase 1 Design Artifacts: Generates data-model.md, interface contracts, and quickstart.md validation guides from the feature spec. - Extension Hooks: Executes optional and mandatory before/after plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature specification with spec-kit, invoke this Skill to produce a complete implementation plan with research findings, entity models, API contracts, and a quickstart validation guide. ## Quick Start Ask the assistant 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 with spec-kit?▼

Run the plan workflow, which executes setup-plan.sh to locate the feature spec, loads the constitution, then produces research.md, data-model.md, contracts, and quickstart.md. Unknowns in the technical context are marked NEEDS CLARIFICATION and resolved during Phase 0 research.

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

The workflow produces research.md with decisions and rationale, data-model.md with entities and validation rules, interface contracts under the contracts directory, and quickstart.md with runnable validation scenarios. It reports the branch and plan path on completion.

Does the plan workflow require a spec-kit project structure?▼

Yes, it requires a .specify directory containing the setup-plan script, memory/constitution.md, and the plan template. Without this structure the setup step cannot resolve the feature spec and plan paths.

How do extension hooks work in the plan workflow?▼

Hooks are read from .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Mandatory hooks are executed automatically before continuing, while optional hooks are presented for manual invocation; hooks with conditions are skipped.

What happens when the constitution check fails during planning?▼

Gate violations cause an ERROR unless they are justified in the plan. The constitution check is evaluated once during initial planning and again after Phase 1 design to confirm compliance.