skills.rest
nico0695
nico0695COMMUNITY
Explore all skills by this author →
GitHub

sddl-design

Generates technical design documents from specification files for the sdd-lite workflow.

Updated Apr 2, 2026
Search Tags:#workflow#architecture#state management#technical design#design document#spec-driven development#sdd-lite
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill sddl-design-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sddl-design
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/sdd-lite/skills/sddl-design
Command: npx skills add https://github.com/nico0695/ai-tools --skill sddl-design-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an approved specification into a concrete technical design, so implementation planning starts from documented architecture decisions instead of guesswork. ## Core Features & Use Cases - Spec-to-Design Conversion: Reads spec.md and produces design.md covering technical approach, affected areas, interfaces, data, and state. - Decision Tracking: Resolves or carries forward every row of the spec's Open Questions And Decisions table so no decision disappears silently. - Proportional Design: Produces a minimal design for single-surface, low-risk changes and a full artifact otherwise. - Use Case: After the sddl-spec stage approves a feature specification, run this stage to generate design.md with architecture decisions and trade-offs, then hand off to sddl-plan for execution planning. ## Quick Start Run the sddl-design stage on the current change to generate design.md from spec.md.

Frequently Asked Questions about sddl-design

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

FAQPage Schema
How do I create a technical design document from a specification?▼

Run the sddl-design stage with a spec.md file as input. It reads the specification's scope and open questions, then writes design.md containing the technical approach, affected areas, interfaces, alternatives, and open technical questions.

What is the difference between sddl-design and sddl-plan?▼

sddl-design produces the architecture and technical decisions in design.md, while sddl-plan produces the stage-by-stage execution plan. The design stage explicitly does not create execution plans or implement code.

When does sddl-design produce a minimal design instead of a full one?▼

A minimal design is produced when no unresolved design-stage questions exist, the spec touches a single surface, and no open risk is medium severity or above. Otherwise the full artifact with all sections is generated.

What happens to unresolved open questions from the spec?▼

Questions needed before design are resolved and recorded in the design; questions needed before execution are carried into Open Technical Questions with their Needed Before value intact. No row is dropped without a recorded resolution or explicit carry-forward.

When should I not use the sddl-design stage?▼

Do not use it to redefine scope or acceptance criteria, which belong to sddl-spec, or to write execution plans, which belong to sddl-plan. It also returns blocked when the spec input is insufficient for a reliable design.

Related Skills

Explore More Software Engineering Skills→
nico0695nico0695

sddl-spec

Formalizes proposal.md into spec.md with scope boundaries and acceptance criteria.

Community
Advanced
nico0695nico0695

sddl-plan

Generates staged execution plans with dependencies and validation strategy from design documents.

Community
Advanced
Sharper-FlowSharper-Flow
4

adv-improve

Analyze repository state to identify evidence-backed improvement opportunities across security, reliability, and architecture.

Official
Advanced
SgtPookiSgtPooki
1

writing-spec

Write ADRs, RFCs, design specs, and requirement documents with testable statements.

Community
Intermediate