speckit-plan

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

Updated May 5, 2026
One-click install
npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill speckit-plan-nikegeorgian-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/nikegeorgian-stack/otgruzka-tovara/tree/main/.cursor/skills/speckit-plan
Command: npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill speckit-plan-nikegeorgian-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete implementation plan requires resolving technical unknowns, designing data models, and defining contracts, which is time-consuming when done manually. ## Core Features & Use Cases - Planning Workflow Execution: Runs the spec-kit plan workflow via setup-plan.ps1, filling the Technical Context and Constitution Check sections of the plan template. - Design Artifact Generation: Produces 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 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 automatically generate the full Phase 0 research and Phase 1 design artifacts for the feature branch. ## Quick Start Run the speckit-plan skill to generate the implementation plan and design artifacts for my current feature specification.

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 workflow 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 plan workflow produce?▼

The workflow produces research.md with resolved clarifications, 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 and memory/constitution.md. Without this structure the setup step cannot locate the feature spec and plan template.

What are extension hooks in the spec-kit plan 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 dispatches research for each unknown and consolidates decisions, rationale, and alternatives into research.md before design begins.