speckit-plan

Name: speckit-plan
Availability: InStock
Author: trungenglish

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

1|Updated Jul 4, 2026

Search Tags:#implementation planning #workflow automation #feature specification #data model #spec-kit #contracts #design artifacts

Ready to run

npx skills add https://github.com/trungenglish/SHOPWISE --skill speckit-plan-trungenglish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/trungenglish/SHOPWISE/tree/main/.cursor/skills/speckit-plan
Command: npx skills add https://github.com/trungenglish/SHOPWISE --skill speckit-plan-trungenglish

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 - Plan Workflow Execution: Runs the spec-kit planning workflow via setup-plan.ps1, filling Technical Context and Constitution Check sections in the plan template. - Design Artifact Generation: Produces research.md, data-model.md, contracts/, and quickstart.md through phased research and design steps. - Extension Hooks: Dispatches optional and mandatory pre/post hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec in a spec-kit project, run this Skill to resolve all NEEDS CLARIFICATION items and generate a complete plan with data models and API contracts. ## Quick Start Ask the AI 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 speckit plan workflow, which 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 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 with a .specify/ directory containing scripts, memory/constitution.md, and optionally extensions.yml. Without this structure the setup script and constitution checks cannot run.

What are extension hooks in the spec-kit plan workflow?▼

Extension hooks are commands defined under hooks.before_plan and hooks.after_plan in .specify/extensions.yml. Mandatory hooks execute automatically via EXECUTE_COMMAND, while optional hooks are suggested for manual execution.

What happens when Technical Context has unresolved unknowns?▼

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