sdd-design

Generate a design.md documenting architecture decisions, data flow, and rationale.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill sdd-design-jnzader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/JNZader/javi-ai/tree/main/delta/overrides/sdd-design
Command: npx skills add https://github.com/JNZader/javi-ai --skill sdd-design-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams produce formal technical design documents that capture architecture decisions, data flows, and implementation rationale for proposed changes.

Core Features & Use Cases

  • Generate a structured design document (design.md) that documents architecture decisions, data flow, file changes, and technical rationale.
  • Act as a dedicated design sub-agent to translate proposals and specifications into a concise, actionable design artifact.
  • Use cases include preparing designs for code changes, feature rollouts, or system redesigns across orchestrators and agents.

Quick Start

Ask the orchestrator to generate a design.md outlining architecture decisions for the pending 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 design document for a proposed system change?

To generate a design document, you provide the proposed change details to the skill, which then produces a structured design.md file capturing architecture decisions, data flow, and technical rationale. It translates proposals into a concise, actionable design artifact for code changes or system redesigns.

What should a technical design doc include for architecture decisions?

A technical design doc should include architecture decisions, data flow mappings, file changes, and implementation rationale. This skill generates these elements in a design.md following project conventions, ensuring the technical reasoning behind proposed changes is formally documented and reproducible.

Can I use this to document data flow and rationale for feature rollouts?

Yes, you can use this skill to document data flow and rationale for feature rollouts. It acts as a dedicated design sub-agent to translate specifications into a comprehensive design artifact, satisfying requirements to formally document architecture decisions across orchestrators and agents.

What is the best way to document technical rationale for code changes?

The best way to document technical rationale for code changes is to generate a comprehensive design document. This skill captures the architecture decisions and technical reasoning in a design.md file, providing a reproducible design artifact that follows your project conventions.

Does this design doc generator work without external dependencies?

Yes, this design doc generator works without external dependencies. It operates as a standalone skill to translate proposals and specifications into a structured design.md artifact, requiring no additional components or environment setup to document your architecture decisions.