speckit.plan

Generates implementation plans and design artifacts from feature specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a written feature specification into a structured implementation plan, eliminating the manual work of drafting research notes, data models, API contracts, and quickstart guides before coding begins. ## Core Features & Use Cases - Plan Setup and Context Loading: Runs the setup-plan script to resolve feature spec, plan, and branch paths, then loads the project constitution for gate checks. - Phase 0 Research: Converts every NEEDS CLARIFICATION item into research tasks and consolidates decisions, rationales, and alternatives into research.md. - Phase 1 Design Artifacts: Generates data-model.md, API contracts under /contracts/, quickstart.md, and updates the agent-specific context file. - Use Case: After writing a feature spec for a new API endpoint, run the planning workflow to produce a complete design package with resolved technical unknowns and constitution compliance checks. ## Quick Start Ask the agent to create an implementation plan for the current feature specification using the speckit plan workflow.

Frequently Asked Questions about speckit.plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation plan from a feature spec?▼

Run the planning workflow, which executes the setup-plan script to locate the feature spec and plan template, then fills in technical context, resolves unknowns through research, and produces design artifacts like data-model.md and contracts.

What artifacts does the speckit planning workflow generate?▼

It generates research.md with resolved decisions, data-model.md with entities and validation rules, API contracts under the contracts directory, quickstart.md, and an updated agent-specific context file.

What happens when technical context has unresolved unknowns?▼

Each NEEDS CLARIFICATION item becomes a research task in Phase 0. The workflow consolidates findings into research.md with decisions, rationales, and alternatives before proceeding to design.

Does the planning workflow enforce project constitution rules?▼

Yes, it fills the Constitution Check section from the constitution file and evaluates gates both before and after design. It stops with an error if violations are unjustified or clarifications remain unresolved.

What are the limitations of the speckit plan command?▼

The command stops after Phase 2 planning and does not break the plan into tasks or implement code. It also depends on repository scripts like setup-plan.sh and update-agent-context.sh being present.