skills.rest
aroca89
aroca89COMMUNITY
Explore all skills by this author →
WebsiteGitHub

sdd-design

Produce architectural change design documents for Spec-Driven Development features.

Updated Apr 8, 2026
Search Tags:#architecture#documentation#sdd#orchestrator#openspec#technical-design#engram
One-click install
npx skills add https://github.com/aroca89/roca_teams --skill sdd-design-aroca89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/aroca89/roca_teams/tree/main/skills/sdd-design
Command: npx skills add https://github.com/aroca89/roca_teams --skill sdd-design-aroca89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guarantees that every Spec-Driven Development change receives a precise technical design covering architecture decisions, data flow, and file-level changes so subsequent implementers and reviewers stay aligned and the orchestrator can progress without missing context.

Core Features & Use Cases

  • Design synthesis: Ingests proposal and spec artifacts to produce the definitive design.md that maps high-level goals to concrete steps and decisions.
  • Persistence-aware workflows: Respects engram, openspec, hybrid, and none modes by fetching the right sources, writing files when required, and always calling mem_save for engram-backed storage.
  • Adaptive coordination: Reads the codebase before designing, follows shared conventions, and returns the structured envelope that downstream phases depend on.

Quick Start

Ask the orchestrator to launch this skill once the proposal and specs are ready so it can compose and store the technical design document.

Frequently Asked Questions about sdd-design

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

FAQPage Schema
What is a Spec-Driven Development technical design blueprint?▼

A Spec-Driven Development technical design blueprint is an architectural document that captures decisions, data flow, and file-level changes to keep implementers aligned and provide context for orchestrator-driven workflows.

How do I generate a design.md document for feature architecture changes?▼

Generate a design.md document by retrieving proposal and spec artifacts, reading the codebase for conventions, and synthesizing the high-level goals into concrete architectural steps and file-level changes.

Does this technical design workflow support different persistence modes?▼

Yes, this technical design workflow supports engram, openspec, hybrid, and none persistence modes, fetching the correct sources and writing files or calling mem_save according to the active mode rules.

When do I need to draft technical design documents in orchestrator-driven development?▼

Draft technical design documents in orchestrator-driven development once proposal and spec artifacts are ready, ensuring the orchestrator can progress to implementation without missing architectural context or decisions.

What are the limitations of automated technical design generation for software architecture?▼

Automated technical design generation relies strictly on pre-existing proposal and spec artifacts; it cannot invent missing context and requires the active persistence mode to correctly fetch sources and store the final design.

Related Skills

Explore More Software Engineering Skills→
bacocobacoco
67

openspec-change-proposal

Generate OpenSpec change proposals with tasks and delta specifications.

Community
Basic
simonheimlichersimonheimlicher
1

architecting-python

Generate Architecture Decision Records for Python architecture decisions.

Community
Advanced
NooBatNooBat

plan

Generate phased, design-driven implementation plans from codebase scans.

Community
Advanced
adacosdevadacosdev

sdd-design

Generate technical design documents with architecture decisions and data flows.

Community
Advanced