skills.rest
zMynxx
zMynxxCOMMUNITY
Explore all skills by this author →
GitHub

sdd-design

Create technical design documents from software change proposals and specifications.

Updated Jun 5, 2026
Search Tags:#architecture#software design#technical design#codebase analysis#sdd#engineering workflow
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-design-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/sdd-design
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-design-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams turn change proposals and specifications into structured technical designs, reducing ambiguity before implementation begins.

Core Features & Use Cases

  • Architecture Planning: Produces design documents covering technical approaches, architecture decisions, data flow, interfaces, and file changes.
  • SDD Workflow Support: Guides spec-driven development phases by connecting proposals, specifications, implementation details, and persistence workflows.
  • Use Case: When a team approves a software change, use this Skill to create a concise implementation design that developers can follow before writing code.

Quick Start

Use the sdd-design skill to create a technical design document for the approved change proposal.

Frequently Asked Questions about sdd-design

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

FAQPage Schema
How do I create technical design documents from software change proposals?▼

This Skill transforms approved software change proposals and specifications into structured technical design documents, covering architecture decisions, data flow, interfaces, and file changes for developers to follow.

What is spec-driven development and how does it fit into architecture planning?▼

Spec-driven development connects proposals, specifications, implementation details, and persistence workflows. This Skill guides those phases by producing engineering change preparation documents that define the technical approach before coding begins.

What should a technical design document include for a software change?▼

A technical design document for a software change should include technical approaches, architecture decisions, data flow, file changes, interfaces, testing strategy, and migration considerations to define the implementation approach.

When do I need to generate an implementation design for codebase analysis?▼

You need to generate an implementation design when a software change is approved but before coding begins, turning specifications into concise technical designs that reduce ambiguity and guide developers through the engineering workflow.

Can I use this for engineering change preparation without prior architecture specifications?▼

No, this Skill requires structured software change proposals and specifications as input. It transforms existing specifications into technical design documents rather than generating architecture decisions from unstructured ideas.

Related Skills

Explore More Software Engineering Skills→
tuliopc23tuliopc23

openspec-propose

Generate design, specification, and task artifacts via the openspec CLI.

Community
Intermediate
richardmbaileyrichardmbailey

rb-explain-diff

Generate interactive HTML walkthroughs for code changes with validation.

Community
Advanced
simonheimlichersimonheimlicher
1

architecting-python

Generate Architecture Decision Records for Python architecture decisions.

Community
Advanced
GACLoveGACLove
2

aily-doc-technical-solution

Generate comprehensive technical solution documents for Feishu cloud output.

Community
Advanced