speckit-plan

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-plan-wu-mao-chia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/WU-MAO-CHIA/AI_tset_platfrom/tree/main/.opencode/skills/speckit-plan
Command: npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-plan-wu-mao-chia

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 - Automated Planning Workflow: Runs the spec-kit plan workflow to fill Technical Context, perform Constitution Checks, and evaluate design gates. - Research & Design Artifacts: Generates research.md, data-model.md, contracts/, and quickstart.md from the feature spec. - Extension Hooks: Supports optional and mandatory pre/post hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec with spec-kit, invoke this Skill to produce a complete implementation plan with resolved clarifications and interface contracts. ## Quick Start Run the speckit-plan skill to generate an implementation plan and design artifacts from 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?▼

Invoke the speckit-plan skill in a spec-kit project. It runs 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 and contracts.

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, quickstart.md, and an updated agent context file.

Does speckit-plan require a specific project structure?▼

Yes, it requires a spec-kit project structure with a .specify directory containing scripts, memory/constitution.md, and the feature spec. Without this structure the setup step cannot locate the required files.

What happens when Technical Context contains NEEDS CLARIFICATION?▼

Each NEEDS CLARIFICATION item becomes a research task in Phase 0. The findings are consolidated into research.md with decisions, rationales, and alternatives, and the workflow errors if clarifications remain unresolved.

How do extension hooks work in the planning workflow?▼

If .specify/extensions.yml defines hooks under before_plan or after_plan, the skill lists or executes them based on their optional flag. Hooks with enabled set to false or with non-empty conditions are skipped.