speckit-plan

Generates implementation plans and design artifacts from feature specifications.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-plan-base-analitica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/Base-Analitica/mouse-hub/tree/main/.jcode/skills/speckit-plan
Command: npx skills add https://github.com/Base-Analitica/mouse-hub --skill speckit-plan-base-analitica

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 error-prone when done ad hoc. This Skill automates the spec-kit planning workflow so design artifacts are generated consistently. ## Core Features & Use Cases - Plan Workflow Execution: Runs the setup script, loads the feature spec and project constitution, and fills the plan template with technical context and constitution checks. - Design Artifact Generation: Produces research.md, data-model.md, contracts/, and quickstart.md through structured Phase 0 and Phase 1 workflows. - Extension Hook Support: Executes optional and mandatory before/after plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec in a spec-kit project, invoke this Skill to resolve open questions, model entities, define interface contracts, and produce a validation quickstart guide. ## Quick Start Ask the agent 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?▼

Run the plan workflow in a spec-kit project, which executes setup-plan.sh, loads the feature spec and constitution, then fills the plan template. It produces research.md, data-model.md, contracts, and quickstart.md as design artifacts.

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

The workflow generates research.md resolving open questions in Phase 0, then data-model.md, interface contracts, and quickstart.md in Phase 1. It also reports the branch and implementation plan path upon completion.

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

Yes, it requires a .specify directory containing scripts, memory/constitution.md, and the plan template. Without this structure the setup script and context loading steps cannot run.

What happens when technical context has unresolved questions?▼

Items marked NEEDS CLARIFICATION become research tasks in Phase 0. Each unknown is investigated and consolidated into research.md with decisions, rationale, and alternatives before design proceeds.

How do extension hooks work in the plan workflow?▼

Hooks defined in .specify/extensions.yml under before_plan and after_plan are executed based on their optional flag. Mandatory hooks run automatically and block progress, while optional hooks are presented for manual execution.