sdd-design

Create a design.md documenting architecture decisions and data flow from a change proposal.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-design-maxculen86
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/maxculen86/coding-bro-ai/tree/main/internal/assets/skills/sdd-design
Command: npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-design-maxculen86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a formal technical design document that captures architecture decisions, data flow, and implementation rationale from a change proposal.

Core Features & Use Cases

  • Generate a complete design.md detailing architecture decisions, data flow diagrams, and implementation rationale.
  • Integrate with Engram/OpenSpec workflows to persist or surface the design as required.
  • Use Case: when a change is proposed, produce a design document outlining decisions, interfaces, and file changes.

Quick Start

Generate a design.md for the latest change proposal using the orchestrator prompt.

Frequently Asked Questions about sdd-design

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

FAQPage Schema
How do I generate an architecture design document from a change proposal?

To generate an architecture design document, the skill loads a change proposal and specs to produce a design artifact capturing architecture decisions, data flow, dependencies, and implementation rationale. It automatically details interfaces and file changes for the proposed modules.

What is a technical design doc and what should it include for multi-module changes?

A technical design doc records architecture decisions and technical rationale for changes spanning multiple modules and interfaces. It should comprehensively detail data flow, dependencies, and the specific implementation approach to guide development.

Can I persist design documents using OpenSpec or Engram workflows?

Yes, you can persist design documents using configured persistence modes including Engram, OpenSpec, hybrid, or none. This integrates the generated design artifact directly into your existing engineering documentation workflows.

What do I need to create a design doc for a proposed software change?

You need to provide the change proposal and existing specifications. The skill requires loading these inputs to analyze the proposed changes across modules and interfaces before generating the formal design artifact.

When should I write a formal design document instead of just implementing the change?

You should write a formal design document when a change proposal spans multiple modules and interfaces, requiring recorded architecture decisions, data flow mapping, and implementation rationale to ensure technical alignment before development.