speckit-plan

Generates implementation plans and design artifacts from feature specifications using the spec-kit planning workflow.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/gkuga/monit-rs --skill speckit-plan-gkuga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/gkuga/monit-rs/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/gkuga/monit-rs --skill speckit-plan-gkuga

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 - Automated Planning Workflow: Runs the spec-kit plan template to fill Technical Context, perform Constitution Checks, and evaluate design gates. - Research and Design Artifacts: Generates research.md, data-model.md, contracts/, and quickstart.md through structured Phase 0 and Phase 1 workflows. - Extension Hooks: Supports optional and mandatory before/after plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec with spec-kit, invoke this Skill to produce a complete implementation plan with resolved technical decisions and interface contracts. ## Quick Start Ask the AI to run the speckit-plan workflow to generate the implementation plan and design artifacts for the current feature specification.

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, which executes setup-plan.sh to locate the feature spec and plan template, then fills Technical Context, resolves unknowns in research.md, and produces data-model.md and contracts.

What artifacts does the spec-kit planning workflow produce?

The workflow produces research.md with resolved technical decisions, data-model.md with entities and validation rules, a contracts directory for external interfaces, quickstart.md, and an updated agent context file.

Does speckit-plan require a specific project structure?

Yes, it requires a spec-kit project with a .specify directory containing scripts like setup-plan.sh and update-agent-context.sh, plus a memory/constitution.md file for gate evaluation.

What happens when Technical Context has unresolved unknowns?

Unknowns are marked as NEEDS CLARIFICATION and converted into research tasks during Phase 0. The workflow dispatches research for each unknown and consolidates decisions, rationale, and alternatives in research.md.

Can I hook custom commands into the planning workflow?

Yes, define hooks under hooks.before_plan or hooks.after_plan in .specify/extensions.yml. Hooks can be optional or mandatory, and disabled hooks or invalid YAML are skipped silently.