sdd-design

Generate a technical design document detailing architecture, data flow, and implementation specifics.

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

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, ensuring that architecture decisions, data flow, and file changes are clearly documented for software development projects.

Core Features & Use Cases

  • Technical Design Generation: Produces a design.md file outlining the technical approach, architecture decisions, data flow, file changes, and testing strategy.
  • Integration with Workflow: Works within a defined artifact store mode (engram, openspec, hybrid, none) to retrieve dependencies and persist results.
  • Use Case: When a new feature is proposed, this Skill can be triggered to generate the detailed technical design document required before implementation begins.

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 new software features?

To generate a technical design document, this Skill analyzes your codebase patterns and outputs a design.md file detailing architecture decisions, data flow, file changes, and testing strategy for your software development project.

What is included in an automated software design document?

An automated software design document includes the technical approach, architecture decisions, data flow mapping, specific file changes, and a comprehensive testing strategy to guide implementation.

Can I persist technical design documents using engram or openspec modes?

Yes, you can persist technical design documents using engram, openspec, hybrid, or none artifact store modes to retrieve dependencies and save your generated design artifacts.

Do I need to analyze existing codebase patterns before creating architecture documentation?

Yes, reading existing codebase patterns is required before creating architecture documentation, as the Skill uses these patterns to ensure the generated technical design aligns with your current software structure.

What is the best way to document data flow and file changes for software development?

The best way to document data flow and file changes is to automate technical design generation, which reads your codebase and outputs a structured design.md file covering all implementation specifics.

When should I generate a technical design document before implementation begins?

You should generate a technical design document whenever a new feature is proposed, ensuring architecture decisions and data flow are clearly documented before the actual software implementation begins.