skills.rest
dallay
dallayOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sdd-design

Generate technical design documents for proposed code changes.

Updated Apr 14, 2026
Search Tags:#design#architecture#codebase#openspec#technical-design#design-doc#testing-strategy
One-click install
npx skills add https://github.com/dallay/opencode-docker --skill sdd-design-dallay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/sdd/sdd-design
Command: npx skills add https://github.com/dallay/opencode-docker --skill sdd-design-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a clear, implementable technical design document for a proposed code change by analyzing the repository, mapping architecture decisions, and specifying concrete file-level changes and testing strategy.

Core Features & Use Cases

  • Code-aware design creation: Reads the codebase and existing patterns to produce a design.md that aligns with the project's conventions.
  • Concrete deliverables: Documents architecture decisions with rationale, data flow diagrams, file changes, interfaces/contracts, testing strategy, and migration/rollout notes.
  • Openspec integration: Stores outputs under openspec/changes/{change-name}/design.md and returns a structured envelope with status, artifacts, and next steps for follow-up sdd tasks.

Quick Start

Provide the change name plus the proposal and specs under openspec/changes/{change-name}/ and ask the skill to write the design.md.

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 code change?▼

A technical design document maps architecture decisions, data flow diagrams, file-level modifications, and testing strategies by analyzing an existing codebase alongside a provided change proposal and specifications.

What should a technical design doc include for mapping file-level code changes?▼

It should include architecture decisions with rationale, data flow diagrams, concrete file modifications, interfaces or contracts, a testing strategy, and migration or rollout notes for clear implementation.

How do I write a design doc that aligns with existing codebase architecture patterns?▼

Writing a design doc that aligns with codebase architecture requires analyzing the repository and existing patterns to ensure proposed file changes and interfaces match the project's established conventions.

Can I automate technical design creation for openspec changes?▼

Yes, you can automate technical design creation for openspec changes by providing the change name, proposal, and specs under the openspec/changes/{change-name}/ directory to generate the design.md file.

What testing strategy and migration notes are needed in a software design document?▼

A software design document needs a testing strategy defining how file-level changes are verified, alongside migration notes detailing the rollout steps for integrating the new architecture into the codebase.

Does generating a design doc require an existing proposal and specs?▼

Yes, generating a design doc requires an existing proposal and specs under the openspec/changes/{change-name}/ directory to analyze the codebase and produce actionable architecture decisions, data flow, and file modifications.

Related Skills

Explore More Software Engineering Skills→
tbdavid2019tbdavid2019
32

openspec-propose

Creates OpenSpec proposal, design, and task artifacts from a vague request.

Community
Advanced
rhussrhuss
107

writing-plans

Generate implementation plans from validated specifications into actionable tasks.

Community
Basic
kurojskurojs
2

sdd-tasks

Break SDD change proposals into phase-ordered implementation tasks.

Community
Advanced
darsoohoodarsoohoo

recipe-design

Orchestrate codebase analysis, ADR creation, and design documentation workflows.

Community
Advanced