skills.rest
fearovex
fearovexCOMMUNITY
Explore all skills by this author →
GitHub

sdd-design

Generate a design.md documenting architecture decisions, data flow, and file changes.

Updated Aug 27, 2026
Search Tags:#design#architecture#documentation#spec-driven#data-flow#change-management
One-click install
npx skills add https://github.com/fearovex/claude-config --skill sdd-design-fearovex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/fearovex/claude-config/tree/main/skills/sdd-design
Command: npx skills add https://github.com/fearovex/claude-config --skill sdd-design-fearovex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces the technical design with architecture decisions, data flow, and a file change plan.

Core Features & Use Cases

  • Reads prior artifacts (openspec/changes/<change-name>/proposal.md, specs/, ai-context/architecture.md, conventions.md) and uses established project patterns to craft a coherent design.
  • Generates a design.md that documents technical decisions, data flow, and file-change implications, acting as the bridge between requirements and code.
  • Produces a clear file-change plan that maps proposed changes to concrete files and modules, aiding rollout and testing.

Quick Start

Provide a change-name to generate a complete technical design and a file-change plan that aligns with existing specs.

Frequently Asked Questions about sdd-design

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

FAQPage Schema
How do I create a technical design document from a project specification?▼

To create a technical design from a specification, provide a change-name so the tool can read prior artifacts like proposal.md and generate a design.md documenting architecture decisions, data flow, and file-change plans.

What is the best way to map data flow and file changes for a new feature?▼

Mapping data flow and file changes requires analyzing existing code patterns and prior specs to produce a concrete file-change plan that bridges requirements and modules for rollout and testing.

How do I document architecture decisions for a spec-driven change?▼

Documenting architecture decisions for a spec-driven change involves reading established project conventions and architecture context to produce a design.md that records technical decisions and testing considerations.

Can I generate a file-change plan from a proposal.md without manual mapping?▼

Yes, you can generate a file-change plan from a proposal.md by applying the design process during the design phase, which automatically maps proposed technical changes to concrete files and modules.

When do I need to produce a technical design for openspec changes?▼

You need to produce a technical design for openspec changes during the design phase, specifically when you have a change described in openspec/changes/ and must bridge requirements with concrete code implementation.

Does spec-driven design work with existing project conventions and architecture?▼

Spec-driven design works with existing project conventions by reading prior artifacts like ai-context/architecture.md and conventions.md to inform decisions and ensure the new design aligns with established patterns.

Related Skills

Explore More Software Engineering Skills→
tiagofurtiagofur

sdd-design

Generate a design.md from proposal.md and specs under openspec/changes.

Community
Advanced
dallaydallay

sdd-design

Generate technical design documents for proposed code changes.

Official
Intermediate
jeanlucianojeanluciano
20

Initializing Project

Initializes Quaestor in projects automating framework detection and generating AGENT.md, ARCHITECTURE.md, CLAUDE.md files.

Community
Advanced
fwdarthfwdarth

sdd-design

Generate technical design documents from proposals and specs.

Community
Intermediate