sdd-design

Generate technical design documents from codebase analysis with architecture decisions and file changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Portmeo/rag-chat-project --skill sdd-design-portmeo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/Portmeo/rag-chat-project/tree/main/.claude/skills/sdd-design
Command: npx skills add https://github.com/Portmeo/rag-chat-project --skill sdd-design-portmeo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive technical design documents, ensuring that the 'how' of a proposed change is clearly articulated before implementation.

Core Features & Use Cases

  • Architecture Decision Recording: Captures key technical choices, alternatives considered, and their rationales.
  • Data Flow Visualization: Describes how data moves through the system, using ASCII diagrams for clarity.
  • File Change Management: Details all modifications, creations, and deletions to project files.
  • Use Case: When a new feature is proposed, this Skill analyzes the existing codebase and generates a design.md file outlining the implementation strategy, architectural decisions, and file modifications required.

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 a proposed software change?

To generate a technical design document, you need a tool that analyzes your existing codebase and outputs architecture decisions, data flow, and file changes. This Skill automates that process by creating a structured design.md file outlining the implementation strategy.

What should be included in an architecture decision record for a new feature?

An architecture decision record should capture key technical choices, alternatives considered, and their rationales. This Skill automates recording these decisions alongside data flow visualizations and file change management within a comprehensive technical design document.

Can I document data flow and file modifications before writing implementation code?

Yes, you can document data flow and file modifications before implementation. This Skill analyzes the codebase to describe data movement using ASCII diagrams and details all necessary file creations, modifications, and deletions in a design document.

What is the best way to plan a testing strategy during technical design?

The best way to plan a testing strategy during technical design is to document it alongside architecture decisions and file changes. This Skill generates a comprehensive technical design document that includes a defined testing strategy for the proposed software change.

Does this design document generator require any specific dependencies?

No, this design document generator does not require any specific dependencies to function. It operates independently to analyze your codebase and output a strictly formatted technical design document detailing implementation plans and architectural decisions.

When do I need a strict format for technical planning and codebase analysis?

You need a strict format for technical planning when multiple stakeholders require clarity and consistency before implementation begins. This Skill adheres to a standardized format to ensure architecture decisions, data flow, and file modifications are clearly articulated.