sdd-plan

Generate an implementation plan from a specification document with component breakdown, risks, and dependencies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill generates a detailed implementation strategy from a given specification, breaking it down into manageable components and identifying potential risks.

Core Features & Use Cases

  • Component Breakdown: Divides a spec into logical, ordered components.
  • Risk Identification: Highlights potential risks and suggests mitigations.
  • Dependency Mapping: Visualizes component dependencies with a Mermaid graph.
  • Use Case: You have a new feature specification (spec.md) and need a clear roadmap for development. This skill will analyze the spec, understand the existing codebase, and produce a plan.md outlining the steps, dependencies, and risks involved.

Quick Start

Use the sdd-plan skill to create an implementation strategy for the spec located in the 'my-feature' directory.

Frequently Asked Questions about sdd-plan

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

FAQPage Schema
How do I create an implementation plan from a software specification document?

Generating an implementation strategy from a spec involves analyzing your specification document alongside the existing codebase. This process breaks the spec into ordered components, identifies potential risks, and maps dependencies to produce a structured plan.md roadmap.

What is the best way to map component dependencies before starting development?

Mapping component dependencies is handled by generating a Mermaid graph within your implementation strategy. This visualizes the relationships between spec components, ensuring you understand the structural connections before executing the development workflow.

How do I identify potential risks in a feature specification?

Identifying risks in a feature specification requires analyzing the spec against your existing codebase and research notes. This Skill highlights potential risks automatically during the planning phase and suggests mitigations to ground your development strategy in reality.

Can I use this planning strategy for an existing codebase or only new projects?

You can use this implementation planning strategy for existing codebases, as it explicitly requires analyzing your current code structure and research notes. This grounds the generated plan.md in your project's actual reality rather than treating it as a blank slate.

Do I need a specific format for my specification document to generate a development plan?

You need a text-based specification document, typically named spec.md, to generate a development plan. The Skill reads this spec alongside your existing codebase to produce a structured plan.md outlining steps, dependencies, and risks.