sdd-design

Create detailed technical architecture documents as structured markdown files.

1|Updated Apr 7, 2026

Search Tags:#design #architecture #software engineering #technical documentation #system planning

Ready to run

npx skills add https://github.com/carlosamesar/framework-sdd --skill sdd-design-carlosamesar

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive technical design documents, saving engineers time in documenting architecture decisions, data flows, and implementation plans.

Core Features & Use Cases

Design Generation: Automatically produce detailed markdown documents outlining system architecture, decisions, and data movement based on change proposals.
Use Case: When a developer needs a design document for a system update, this Skill compiles a structured plan including file modifications, interfaces, and testing strategies.
Technical Rationale: Ensures design consistency, enforces documentation standards, and accelerates architectural reviews.

Quick Start

Instruct the AI to produce a technical design document for the specified change using available proposals and codebase information.

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 system changes?▼

You generate a technical design document by analyzing code repositories and proposals to produce structured markdown files outlining architecture decisions, data flow, and implementation plans. This ensures clear traceability and quality assurance for project teams.

What should a software architecture document include for implementation planning?▼

A software architecture document should include system architecture decisions, data movement, file modifications, interfaces, testing strategies, and implementation plans. This ensures design consistency and accelerates architectural reviews for engineering teams.

Can I automate technical documentation generation from existing code repositories?▼

Yes, you can automate technical documentation generation by analyzing code repositories and change proposals. The process produces detailed markdown files covering architecture decisions, data flow, and testing strategies, saving engineers time on documentation.

Does this technical design approach work without external dependencies?▼

Yes, this technical design approach works without external dependencies. It analyzes code repositories and proposals independently to produce structured markdown files, requiring no additional environment setup or external libraries to function.

What is the best way to document data flow and architecture decisions for software updates?▼

The best way to document data flow and architecture decisions is generating structured markdown files that compile system plans including file modifications, interfaces, and testing strategies. This enforces documentation standards and ensures design consistency across updates.