skills.rest
tiagofur
tiagofurCOMMUNITY
Explore all skills by this author →
GitHub

sdd-design

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

Updated Feb 12, 2026
Search Tags:#automation#design#architecture#documentation#openspec#change-management
One-click install
npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-design-tiagofur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/tiagofur/kakoclaw/tree/main/.claude/skills/sdd-design
Command: npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-design-tiagofur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create technical design documents efficiently by transforming proposals, specs, and code references into a structured, architecture-focused design.md that captures decisions and rationale.

Core Features & Use Cases

  • Generate a complete design document from a proposal, specs, and delta changes, ensuring consistency with organizational templates.
  • Capture architecture decisions, data flow, file changes, and technical rationale to guide implementation and future maintenance.
  • Use Case: When a change needs formal design documentation, run this skill to produce openspec/changes/{change-name}/design.md with all required sections.

Quick Start

Provide a complete design.md for the latest change using the orchestrator inputs (proposal.md, specs/), and store it under openspec/changes/{change-name}/design.md.

Frequently Asked Questions about sdd-design

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

FAQPage Schema
How do I generate technical design documents from a feature proposal?▼

To generate technical design documents, you can transform a feature proposal, specs, and existing code references into a structured design.md. This captures architecture decisions, data flow, file changes, and rationale to guide implementation.

What is the best way to document architecture decisions for OpenSpec changes?▼

Documenting architecture decisions for OpenSpec changes involves creating a design.md file under openspec/changes/{change-name}/. This file captures the technical rationale, data flow, and file changes required by the OpenSpec template.

Can I automate design documentation using existing specs and proposal files?▼

Yes, you can automate design documentation by processing proposal.md and specs/ directory inputs. The skill transforms these inputs into a complete technical design document that ensures consistency with organizational templates.

Do I need existing code references to create a complete technical design document?▼

Yes, existing code references are used alongside proposal.md and specs/ to produce the design.md. They provide the necessary context for capturing accurate file changes and architecture decisions within the design document.

What should be included in an OpenSpec design template for change management?▼

An OpenSpec design template for change management should include architecture decisions, data flow, file changes, and technical rationale. These sections ensure the design document effectively guides implementation and future maintenance.

Related Skills

Explore More Software Engineering Skills→
memorysavermemorysaver

openspec-sync-specs

Merge delta specs under openspec/changes into main specs.

Community
Intermediate
tungnguyen10tungnguyen10

openspec-apply-change

Automate implementation of OpenSpec change tasks with progress tracking.

Community
Advanced
aditriokaaditrioka

next-change

Identify and claim the next OpenSpec change for the nearyou-id project.

Community
Advanced
jankneumannjankneumann
4

plan-roadmap

Decompose markdown proposals into prioritized OpenSpec change candidates with a dependency DAG.

Community
Advanced