sdd-design

Name: sdd-design
Availability: InStock
Author: thiagoooo34252

Create technical design documents in markdown from proposal and specification documents.

1|Updated Apr 12, 2026

Search Tags:#software architecture #technical design #programming #code documentation #design document creation

Ready to run

npx skills add https://github.com/thiagoooo34252/atlas-engineer --skill sdd-design-thiagoooo34252

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/thiagoooo34252/atlas-engineer/tree/main/skills/sdd-design
Command: npx skills add https://github.com/thiagoooo34252/atlas-engineer --skill sdd-design-thiagoooo34252

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 documents, streamlining the process and ensuring consistency.

Core Features & Use Cases

Technical Design Document Creation: Generates a comprehensive design document based on provided proposal and specifications.
Architecture Decision Documentation: Captures architecture decisions, data flow, file changes, and technical rationale.
Use Case: When an engineer needs to document the technical design for a change, this Skill can automate the process, ensuring all necessary information is included.

Quick Start

Use the sdd-design skill to create a technical design document for the 'new-architecture' change.

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 software architecture changes?▼

To generate a technical design document, you need to provide the proposal and specification documents as input. The skill reads these files and produces a structured markdown design document that captures architecture decisions, data flow, file changes, and technical rationale.

What should a technical design document include for software engineering projects?▼

A technical design document should include architecture decisions, data flow, file changes, and technical rationale. Automating this process ensures all necessary information is captured consistently by utilizing your established project standards and conventions during document generation.

Can I use project standards and conventions to generate code documentation automatically?▼

Yes, you can enforce project standards and conventions when generating code documentation and design documents. The skill utilizes your project's established standards to ensure the resulting markdown technical design document remains consistent with your existing engineering practices.

What's the best way to document architecture decisions and data flow for a new software change?▼

The best way to document architecture decisions and data flow is to automate the process using your proposal and specification documents. This ensures the technical rationale and file changes are captured comprehensively in a markdown design document without manual formatting overhead.

Do I need to write proposal and specification documents before automating design document creation?▼

Yes, you need to provide proposal and specification documents before automating design document creation. The skill requires reading these inputs to accurately generate a technical design document in markdown format that reflects the proposed software changes.