sdd-planning

Convert specifications into technical plans with architecture and phased roadmaps.

192|21|Updated Sep 19, 2025
One-click install
npx skills add https://github.com/madebyaris/spec-kit-command-cursor --skill sdd-planning-madebyaris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-planning
Source: https://github.com/madebyaris/spec-kit-command-cursor/tree/main/.cursor/skills/sdd-planning
Command: npx skills add https://github.com/madebyaris/spec-kit-command-cursor --skill sdd-planning-madebyaris

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill helps teams translate written specifications into concrete, actionable technical plans, reducing ambiguity and accelerating design and implementation.

Core Features & Use Cases

  • Architecture design planning: transform requirements into components, interfaces, and data flows.
  • Roadmap & phased implementation: generate setup → core → integration → polish plans with milestones and risk mitigations.
  • Documentation generation: produce architecture docs and diagrams from specs for stakeholder alignment.

Quick Start

Use the sdd-planning skill to convert a completed specification into a detailed technical plan that includes an architecture overview and implementation roadmap.

Frequently Asked Questions about sdd-planning

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

FAQPage Schema
How do I turn written specifications into actionable architecture plans?

Converting written specifications into actionable architecture plans involves transforming requirements into structured components, interfaces, and data flows. This process reduces ambiguity and accelerates both system design and implementation preparation.

Can I generate a phased implementation roadmap from a system design document?

Generating a phased implementation roadmap from a system design document produces setup, core, integration, and polish plans. Each phase includes specific milestones and risk mitigations to guide the technical execution.

What is the best way to create architecture diagrams and data models from technical specs?

Creating architecture diagrams and data models from technical specs involves processing written requirements to produce structured documentation. This output ensures stakeholder alignment by visualizing component breakdowns and system flows.

Does this approach to architecture planning work for component breakdown and interface design?

Architecture planning through specification conversion supports component breakdown and interface design by transforming written requirements into structured technical plans. It delivers actionable outputs across both software and systems implementation.

When do I need to convert specifications into technical plans?

Converting specifications into technical plans is needed when teams must translate written requirements into concrete architecture designs. It reduces ambiguity during the transition from stakeholder documentation to implementation preparation.