speckit-plan

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete technical plan requires research, data modeling, and contract design. This Skill automates that planning workflow inside a spec-kit project, producing structured design artifacts instead of ad-hoc notes. ## Core Features & Use Cases - Plan Workflow Execution: Runs the setup script, loads the feature spec and project constitution, and fills the implementation plan template with technical context. - Research & Design Phases: Phase 0 resolves unknowns into research.md; Phase 1 generates data-model.md, interface contracts, and quickstart.md. - 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 design package (research, data model, contracts, quickstart) ready for task breakdown and implementation. ## Quick Start Run the speckit-plan skill 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, loads the feature spec and constitution, then fills the plan template and produces research.md, data-model.md, contracts, and quickstart.md.

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

The workflow produces research.md in Phase 0, resolving all NEEDS CLARIFICATION items, and data-model.md, interface contracts, 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 with a .specify directory containing scripts, memory/constitution.md, and templates. Without this structure the setup script and plan template loading will fail.

How do extension hooks work in the planning workflow?▼

Hooks are defined in .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Mandatory hooks are executed automatically before planning continues, while optional hooks are only suggested with their command and prompt.

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 after loading context and re-evaluated after the Phase 1 design is complete.