speckit-plan

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

44|10|Updated Mar 28, 2024
One-click install
npx skills add https://github.com/sensein/senselab --skill speckit-plan-sensein
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/sensein/senselab/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/sensein/senselab --skill speckit-plan-sensein

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 produced consistently. ## Core Features & Use Cases - Plan Workflow Execution: Runs the setup script, loads the feature spec and constitution, and fills the implementation plan template with technical context. - Research and Design Phases: Generates research.md to resolve open questions, then produces data-model.md, contracts, and quickstart.md. - Extension Hooks: Checks .specify/extensions.yml for optional or mandatory before/after plan hooks and executes or surfaces them. - Use Case: After writing a feature spec in a spec-kit project, invoke this Skill to produce a complete plan directory with research findings, data models, and API contracts ready for 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?

Invoke the speckit-plan skill inside a spec-kit project. It runs setup-plan.sh, loads the feature spec and constitution, 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 resolving open questions, data-model.md describing 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. Without these, the setup step cannot run.

What happens when technical context has unresolved questions?

Unknowns are marked as NEEDS CLARIFICATION in the Technical Context, then Phase 0 dispatches research tasks for each one. The plan reports an error if gate failures or unresolved clarifications remain.

How do extension hooks work in the planning workflow?

If .specify/extensions.yml exists, hooks under hooks.before_plan and hooks.after_plan are checked. Optional hooks are surfaced for manual execution, while mandatory hooks are executed automatically before continuing.