sdd-design

Generate design.md documents and ADRs from proposals and delta specs.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jota-batuta/batuta-dots --skill sdd-design-jota-batuta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/sdd-design
Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill sdd-design-jota-batuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams produce formal technical design documents and ADRs from proposals, ensuring consistent design governance.

Core Features & Use Cases

  • Generate design.md from a proposal and delta specs.
  • Include architecture decisions, rationale, data flow, and a documentation plan.
  • Apply to multi-change architectural proposals across software projects.

Quick Start

Create openspec/changes/{change-name}/design.md by translating the proposal and delta specs into 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 an architecture decision record from a proposal?

You generate an architecture decision record by translating your proposal and delta specs into a structured design document. This process captures architecture decisions, rationale, data flow, and a documentation plan for multi-change software projects.

What is the best way to document system design rationale for engineering governance?

The best way to document system design rationale is producing formal technical design documents that outline architecture decisions and data flow. This ensures consistent design governance across software projects by providing a comprehensive design plan.

How does a design doc improve task breakdown for architectural changes?

A design doc improves task breakdown by applying structured governance to architectural changes. It transforms proposals into comprehensive plans that detail data flow and architecture decisions, ensuring clear execution across software projects.

Can I use this for multi-part design artifacts across software projects?

Yes, you can use this for multi-part design artifacts across software projects. It applies to architectural changes and task breakdowns, satisfying requirements for architecture decisions, rationale, and a comprehensive design plan.

When do I need a formal ADR for my software architecture?

You need a formal ADR when managing multi-change architectural proposals that require design governance. It produces structured technical design documents capturing decisions and rationale from your initial proposal and delta specs.

What should be included in a technical design document for engineering governance?

A technical design document should include architecture decisions, rationale, data flow, and a documentation plan. It translates proposals and delta specs into a complete design to ensure consistent governance across projects.