sdd-design

Name: sdd-design
Availability: InStock
Author: Gentleman-Programming

Generate formal design documents from proposals and specifications.

1.3k|159|Updated Feb 16, 2026

Search Tags:#design #architecture #documentation #specification #data-flow #design-doc #change-management

Ready to run

npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-design-gentleman-programming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/Gentleman-Programming/agent-teams-lite/tree/main/skills/sdd-design
Command: npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-design-gentleman-programming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate proposals and specs into formal design documents that guide implementation, review, and alignment across teams.

Core Features & Use Cases

Architecture Decisions: Capture rationale, alternatives, and trade-offs for major technical choices.
Data Flow & Interfaces: Map data movement, dependencies, and API contracts across components.
Use Case: When a change touches multiple modules, generate a cohesive design.md detailing scope and impact.

Quick Start

Create a comprehensive design document for the requested change, including architecture decisions, data flow diagrams, and file changes.

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 formal technical design document from a proposal?▼

To create a technical design document, generate a formal design.md from your proposals and specifications. The output enforces structured sections for architecture decisions, data flow mapping, and file changes across your codebase to guide implementation and review.

What should be included in an architecture decision document for software changes?▼

An architecture decision document should capture the rationale, alternatives, and trade-offs for major technical choices. It must also map data movement, dependencies, and API contracts across components to ensure alignment across teams during implementation.

When do I need a formal design document for codebase changes?▼

You need a formal design document when a proposed change touches multiple modules and requires architecture decisions or data flow mapping. Generating a cohesive design.md detailing scope and impact ensures structured change management and team alignment.

How do I map data flow and interfaces for a new software feature?▼

To map data flow and interfaces, document data movement, dependencies, and API contracts across components. This structured approach ensures that technical designs accurately reflect how modules interact and how data is managed within the system.

Can I use this for changes that impact multiple modules across a codebase?▼

Yes, you can use this for changes impacting multiple modules. It generates a cohesive design.md detailing the technical approach, testing strategy, migration, and file changes, providing a comprehensive overview of the scope and impact.