sdd-design

Generate a design.md document from target spec and steering docs.

1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/eburairu/Squat-Tracker --skill sdd-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/eburairu/Squat-Tracker/tree/main/.agent/skills/sdd-design
Command: npx skills add https://github.com/eburairu/Squat-Tracker --skill sdd-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates requirements and a target spec into a concrete design document (design.md), aligning architecture decisions with project goals and reducing ambiguity during handoffs.

Core Features & Use Cases

  • Spec-driven design: read .sdd/target-spec.txt, steering docs, and spec directory to produce a unified design.md.
  • Architecture guidance: outlines system architecture, data models, processing flows, and error handling.
  • Use Case: generate a complete design.md for a given spec, ready for review and implementation.

Quick Start

Provide a target spec in .sdd/target-spec.txt and run the sdd-design process to create .sdd/specs/[spec]/design.md. If a spec outline is missing, follow the prompts to supply product/tech/structure details and requirements.md.

Frequently Asked Questions about sdd-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn software requirements into a technical design doc?

To turn requirements into a technical design doc, provide a target spec in .sdd/target-spec.txt and steering docs. The process synthesizes architecture decisions and outputs a complete design.md with data models, processing flows, and error handling.

What files do I need before generating a design document from a specification?

Generating a design document from a specification requires .sdd/target-spec.txt, steering docs like product.md, tech.md, and structure.md, plus an existing requirements.md file to synthesize architecture decisions successfully.

What is included in an architecture design document generated from a target spec?

An architecture design document generated from a target spec includes a complete architecture overview, data models, processing flows, and error handling details, aligning technical decisions with project goals and reducing ambiguity.

Can I generate a design doc if my spec directory is missing steering information?

If your spec directory is missing steering information, you can still generate a design doc by following the prompts to supply product, tech, and structure details to guide the architecture decisions.

Why use a spec-driven approach for system design documentation?

Use a spec-driven approach for system design documentation to translate requirements and a target spec into concrete architecture decisions, reducing ambiguity during handoffs and aligning system structure with project goals.