sdd-design

Generate technical design documents from proposals and specifications.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/Codenburg/skills --skill sdd-design-codenburg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/Codenburg/skills/tree/main/sdd-design
Command: npx skills add https://github.com/Codenburg/skills --skill sdd-design-codenburg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of technical design and architecture documents for proposed changes, streamlining the process and ensuring clarity in design decisions.

Core Features & Use Cases

  • Technical Design Automation: Automatically generates technical design documents based on proposals and specifications.
  • Architecture Decisions Documentation: Captures architecture decisions, data flow, file changes, and technical rationale.
  • Use Case: When a change is proposed, this Skill can be triggered to create a design document that outlines how the change will be implemented.

Quick Start

Use the sdd-design skill to generate a technical design document for the change 'new-features'.

Frequently Asked Questions about sdd-design

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

FAQPage Schema
How do I automate technical design document creation for proposed software changes?

You can automate technical design document creation by providing proposals and specifications as input to generate a structured design document outlining how the change will be implemented.

What should a technical design document include for software architecture decisions?

A technical design document should include architecture decisions, data flow, file changes, and the technical rationale behind proposed software modifications.

How do I document architecture decisions and file changes for a new feature?

To document architecture decisions and file changes for a new feature, trigger the design generation process using the proposed change name to automatically capture the technical rationale and data flow.

What inputs are required to generate a technical design document?

Generating a technical design document requires proposals and specifications as input to ensure the automated output accurately reflects the proposed software changes.

When do I need to create a technical design document in the software development process?

You need to create a technical design document when a change is proposed in software development, ensuring clear architecture decisions and implementation plans are established before development proceeds.

Can I use automated document generation for change management processes?

Yes, automated document generation applies to technical design and architecture processes in software development, streamlining change management by capturing technical rationale and data flow for proposed modifications.