speckit-plan

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

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/PanyaPrimal/selfHandlerApp --skill speckit-plan-panyaprimal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/PanyaPrimal/selfHandlerApp/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/PanyaPrimal/selfHandlerApp --skill speckit-plan-panyaprimal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, modeling data, and defining contracts, which is slow and inconsistent when done manually. ## Core Features & Use Cases - Plan Workflow Execution: Runs the spec-kit planning workflow via setup-plan.ps1, filling Technical Context and Constitution Check sections in the plan template. - Research and Design Artifacts: Generates research.md to resolve NEEDS CLARIFICATION items, then produces data-model.md, contracts/, and quickstart.md. - Extension Hooks: Executes optional and mandatory before_plan and after_plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec in a spec-kit project, invoke this Skill to produce a complete Phase 0/Phase 1 design package with resolved technical decisions and validation scenarios. ## 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 in a spec-kit project. It executes setup-plan.ps1 to locate the feature spec and plan template, then fills Technical Context, resolves unknowns in research.md, and produces data-model.md, contracts, and quickstart.md.

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, and quickstart.md with runnable validation scenarios.

Does speckit-plan require a specific project structure?

Yes, it requires a spec-kit project with a .specify directory containing scripts/powershell/setup-plan.ps1, memory/constitution.md, and the plan template. Without this structure the setup step cannot run.

What are extension hooks in the planning workflow?

Hooks are commands defined under hooks.before_plan and hooks.after_plan in .specify/extensions.yml. Mandatory hooks are executed automatically before or after planning, while optional hooks are only suggested to the user.

What happens when Technical Context has unresolved items?

Items marked NEEDS CLARIFICATION become research tasks in Phase 0. The workflow consolidates findings in research.md with decisions, rationale, and alternatives before proceeding to Phase 1 design.