speckit-plan

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

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-plan-lluisfont
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/lluisfont/clickup-reporting/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-plan-lluisfont

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, defining data models, and drafting interface 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 implementation plan. - Research & Design Artifacts: Generates research.md, data-model.md, contracts/, and quickstart.md by resolving NEEDS CLARIFICATION items and extracting entities from the feature spec. - Extension Hooks: Executes optional and mandatory pre/post hooks defined in .specify/extensions.yml before and after planning. - Use Case: After writing a feature spec for a new CLI command, run this Skill to produce a complete plan with resolved technical decisions, a data model, API contracts, and a quickstart validation 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, which executes .specify/scripts/powershell/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 plan workflow produce?

The workflow produces research.md resolving all NEEDS CLARIFICATION items, 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 structure with a .specify directory containing the constitution at .specify/memory/constitution.md, PowerShell setup scripts, and a feature spec directory created by earlier spec-kit commands.

How do extension hooks work in the plan workflow?

Hooks are defined in .specify/extensions.yml under hooks.before_plan and hooks.after_plan. Mandatory hooks are executed automatically before continuing, while optional hooks are only suggested, and hooks with non-empty conditions are skipped.

What happens when Technical Context has unresolved unknowns?

Each NEEDS CLARIFICATION item becomes a research task in Phase 0, and findings are consolidated in research.md with decisions, rationale, and alternatives before Phase 1 design begins.