sdd-design

Generate technical design documents detailing architecture decisions, data flow, and file modifications.

1|1|Updated Jul 31, 2025

Search Tags:#architecture #documentation #software development #technical design #implementation plan #design document

Ready to run

npx skills add https://github.com/JoaquinFontaana/alquileres --skill sdd-design-joaquinfontaana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/JoaquinFontaana/alquileres/tree/main/.agents/skills/sdd-design
Command: npx skills add https://github.com/JoaquinFontaana/alquileres --skill sdd-design-joaquinfontaana

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed technical design documents, ensuring that the implementation approach for changes is clearly defined and documented.

Core Features & Use Cases

Architecture Decisions: Documents key technical choices, alternatives considered, and rationale.
Data Flow Visualization: Illustrates how data moves through the system.
File Change Tracking: Lists all files to be created, modified, or deleted.
Use Case: When a new feature is proposed, this Skill can generate the design.md file outlining the technical implementation, including database schema changes, API endpoints, and necessary code modifications.

Quick Start

Use the sdd-design skill to create a technical design for the 'user-authentication' change.

Frequently Asked Questions about sdd-design

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

FAQPage Schema

How do I generate a technical design document for software changes?▼

To generate a technical design document, this Skill analyzes proposal specs, delta specs, and source code to produce a comprehensive design.md artifact detailing architecture decisions, data flow, and file modifications.

What should be included in an implementation plan for a new software feature?▼

An implementation plan should include architecture decisions, data flow visualization, and file change tracking, specifying all files to be created, modified, or deleted for the proposed software feature.

Can I use this to document database schema changes and API endpoints?▼

Yes, you can use this Skill to document database schema changes and API endpoints within the generated design.md file, outlining the complete technical implementation approach for the proposed software changes.

What inputs are required to create a software design document?▼

Creating a software design document requires providing proposal specs, delta specs, and relevant source code for analysis to ensure the technical implementation plan accurately reflects the required architecture and file modifications.

Does this approach support the entire software engineering lifecycle?▼

Yes, this approach supports the software engineering lifecycle by providing a structured method for implementation planning, ensuring the technical approach for software changes is clearly defined and documented before development begins.

When do I need a technical design document instead of just writing code?▼

You need a technical design document when a new feature is proposed and requires clear definition of architecture decisions, data flow, and file modifications before implementation, ensuring all technical choices and rationale are documented.