speckit-plan

Translate feature specifications into phased technical plans with artifacts.

Updated Jan 3, 2026

Search Tags:#automation #planning #architecture #specification #implementation #phases

Ready to run

npx skills add https://github.com/ch-yang1273/2026-Playground --skill speckit-plan-ch-yang1273

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/ch-yang1273/2026-Playground/tree/main/0221-speckit/.agents/skills/speckit-plan
Command: npx skills add https://github.com/ch-yang1273/2026-Playground --skill speckit-plan-ch-yang1273

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms detailed feature specifications into actionable, phased technical plans, reducing ambiguity and guiding architecture, tech choices, and delivery milestones.

Core Features & Use Cases

Generate a complete implementation plan from a spec, including architecture, technology stack, and phased milestones.
Produce artifacts such as research.md, data-model.md, contracts, and quickstart.md to guide development and onboarding.
Validate inputs against a standard plan template, load context from .specify/memory/constitution.md, and update agent context during planning.

Quick Start

Run speckit-plan on a prepared feature spec to generate a complete implementation plan and associated artifacts.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema

How do I turn feature specifications into phased implementation plans?▼

To turn feature specifications into phased implementation plans, run the planning process on a prepared feature spec to generate concrete technical milestones. It validates inputs against a standard plan template and loads context from your constitution.md to guide architecture and delivery.

What artifacts are produced when generating an implementation plan from a spec?▼

Generating an implementation plan from a spec produces artifacts like research.md, data-model.md, contracts, and quickstart.md. These files support development and onboarding by documenting architecture, technology stack choices, and phased delivery milestones.

Do I need a specific template to generate phased technical plans for software projects?▼

Yes, generating phased technical plans for software projects requires a compatible IMPL_PLAN template. The planning process validates your feature spec against this template and loads context from .specify/memory/constitution.md before producing the implementation plan.

How does spec-driven planning handle architecture and technology stack decisions?▼

Spec-driven planning handles architecture and technology stack decisions by translating detailed feature specifications into actionable, phased technical plans. It updates agent context throughout the process, ensuring architecture choices and tech decisions are documented in the generated artifacts.

What is the best way to reduce ambiguity in software feature delivery milestones?▼

The best way to reduce ambiguity in software feature delivery milestones is to use a spec-driven workflow that transforms detailed specifications into actionable technical plans. This process validates inputs and produces structured artifacts like data-model.md and contracts.