speckit-plan

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

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Powerworks/Underwriting --skill speckit-plan-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/Powerworks/Underwriting/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/Powerworks/Underwriting --skill speckit-plan-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete technical plan requires resolving unknowns, designing data models, and defining contracts, which is time-consuming when done manually. This Skill automates the spec-kit planning workflow so design artifacts are generated consistently from your spec. ## Core Features & Use Cases - Automated Plan Setup: Runs the spec-kit setup script to locate the feature spec, plan file, and branch, then loads the project constitution for gate checks. - Phased Design Generation: Phase 0 produces research.md resolving all NEEDS CLARIFICATION items; Phase 1 produces data-model.md, contracts/, and quickstart.md. - Extension Hook Support: Executes optional and mandatory before_plan and after_plan hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec with spec-kit, invoke this Skill to automatically generate the research, data model, API contracts, and quickstart validation guide for the feature branch. ## Quick Start Run the speckit-plan skill with any optional planning guidance 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 with spec-kit?▼

Invoke the speckit-plan skill after creating your feature specification. It runs the setup-plan script, loads the spec and constitution, then generates research.md, data-model.md, contracts, and quickstart.md following the plan template.

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, a contracts directory, 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 the setup-plan script, memory/constitution.md, and the plan template. Without this structure the setup step cannot locate the feature spec and plan files.

How do extension hooks work in the spec-kit plan workflow?▼

Hooks are defined under hooks.before_plan and hooks.after_plan in .specify/extensions.yml. Mandatory hooks are executed automatically, optional hooks are presented for manual invocation, and hooks with enabled set to false are skipped.

What happens when the plan has unresolved clarifications?▼

Unknowns in the Technical Context are marked as NEEDS CLARIFICATION and converted into research tasks in Phase 0. The workflow errors on unresolved clarifications or constitution gate failures rather than proceeding with an incomplete plan.