speckit-plan

Generate implementation plans from feature specifications with phased rollout steps.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/ev3rlit/magam --skill speckit-plan-ev3rlit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/ev3rlit/magam/tree/main/.claude/skills/speckit-plan
Command: npx skills add https://github.com/ev3rlit/magam --skill speckit-plan-ev3rlit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature specifications often remain ambiguous, causing misalignment and rework. This skill converts those specs into a concrete, actionable implementation plan that guides architecture and execution.

Core Features & Use Cases

  • Generates architecture outlines, tech stack recommendations, and phased implementation steps from a feature specification.
  • Produces plan artifacts (plan.md, data-model.md, contracts) to support development and collaboration.
  • Suitable for spec-driven projects seeking repeatable, auditable planning workflows.

Quick Start

Provide the feature specification to the skill and run the planning workflow to generate a complete implementation plan.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I convert a feature spec into an implementation plan?

To convert a feature spec into an implementation plan, provide the specification to the workflow to generate architecture outlines, data models, contracts, and phased rollout steps. This structured planning ensures compliance before execution.

What is spec-driven development planning?

Spec-driven development planning is the process of generating concrete architecture outlines, data models, and phased rollout steps directly from a feature specification. It enforces structured compliance to eliminate ambiguity and reduce rework.

Can I generate data models and API contracts from a feature specification?

Yes, you can generate data models and API contracts from a feature specification by running the planning workflow. It produces plan artifacts including data-model.md and contracts to support structured development and collaboration.

Does structured implementation planning work for any software architecture?

Structured implementation planning works across various architectures by applying templates to guide engineers through research, data-modeling, and phased rollout. It ensures the generated plan remains compliant with the original specification.

What is the best way to prevent ambiguity in feature specifications?

The best way to prevent ambiguity in feature specifications is to convert them into a concrete, actionable implementation plan using structured templates. This enforces specification compliance before development proceeds.

What artifacts are produced when creating a phased rollout plan?

When creating a phased rollout plan, the workflow produces artifacts like plan.md, data-model.md, and API contracts. These files document the architecture outline, tech stack recommendations, and implementation steps for collaboration.