sdd-design

Generate technical design documents with architecture decisions and data flows.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/adacosdev/dotfiles --skill sdd-design-adacosdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/adacosdev/dotfiles/tree/main/dot_config/opencode/skills/sdd-design
Command: npx skills add https://github.com/adacosdev/dotfiles --skill sdd-design-adacosdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a concise technical design document that captures architecture decisions, data flows, implementation approach, and rationale for a proposed change.

Core Features & Use Cases

  • Generates architecture decisions, data-flow diagrams, file change guidance, and rationale to guide implementation.
  • Supports orchestrator-driven design tasks for changes described by a proposal, across engram/openspec/hybrid workflows.
  • Use Case: When planning a major change, generate a design.md that documents decisions, data flow, components, and dependencies for reviewer alignment.

Quick Start

Provide the orchestrator with the change-name and project context to generate and persist a complete design.

Frequently Asked Questions about sdd-design

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

FAQPage Schema
How do I generate a technical design document for architecture decisions?

To generate a technical design document, provide the change-name and project context to the orchestrator. It creates a design.md capturing architecture decisions, data flows, and implementation rationale for reviewer alignment.

What should be included in software architecture documentation for a proposed change?

Software architecture documentation should include architecture decisions, data-flow diagrams, file change guidance, components, dependencies, and implementation rationale to guide development and ensure reviewer alignment.

How do I document data-flow diagrams and implementation rationale for code changes?

Document data-flow diagrams and implementation rationale by triggering design tasks through the orchestrator across engram, openspec, or hybrid workflows, which generates and persists the complete technical design.

Does this design specification workflow support orchestrator-driven hybrid modes?

Yes, the design specification workflow supports orchestrator-driven tasks across engram, openspec, and hybrid modes. It satisfies frontmatter validation and persistence rules while generating comprehensive technical designs.

When do I need a technical design document for software engineering changes?

You need a technical design document when planning a major change. It documents architecture decisions, data flow, components, and dependencies to guide implementation and achieve reviewer alignment before development proceeds.