sdd-design

Generate technical design documents from proposals and specs.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/fwdarth/agent-teams-lite-domainaware --skill sdd-design-fwdarth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-design
Source: https://github.com/fwdarth/agent-teams-lite-domainaware/tree/main/.opencode/skills/sdd-design
Command: npx skills add https://github.com/fwdarth/agent-teams-lite-domainaware --skill sdd-design-fwdarth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation of technical design documents, ensuring that architectural decisions, data flow, and file changes are clearly documented for software development projects.

Core Features & Use Cases

  • Technical Design Generation: Creates design.md files based on proposals and specifications.
  • Architecture Decision Documentation: Captures choices, alternatives, and rationale.
  • File Change Tracking: Lists modifications, creations, and deletions.
  • Use Case: When a new feature is proposed, this Skill can generate the technical design document outlining the implementation strategy, data flow, and necessary file modifications, ensuring consistency and clarity before development begins.

Quick Start

Use the sdd-design skill to write the technical design for the 'user-authentication' 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 technical design document for software changes?

To generate a technical design document, you can use this Skill to automatically create a `design.md` file that details architecture decisions, data flow, file modifications, and testing strategies based on your project proposals and specifications.

What should be included in a software architecture decision document?

A software architecture decision document should capture architectural choices, alternatives, and technical rationale. This Skill automates this by documenting choices and listing necessary file creations, modifications, and deletions for the proposed feature.

How do I document file modifications and data flow for a new feature?

You document file modifications and data flow by outlining the implementation strategy in a technical design document. This Skill reads your proposals and specs to produce a `design.md` artifact that tracks these changes and details the data flow.

Does this technical design generator require any specific frameworks?

This technical design generator operates within the openspec framework. It requires reading existing proposals and specs to produce the `design.md` artifacts and needs adherence to your project conventions to articulate the technical rationale clearly.

Why do I need a technical design document before starting development?

You need a technical design document before development to ensure consistency and clarity. It clearly documents architectural decisions, data flow, and file changes, ensuring that the implementation strategy is thoroughly outlined and reviewed before coding begins.

Can I use this to track file changes and testing strategies for software architecture?

Yes, you can use this Skill to track file changes and document testing strategies. It generates technical design documents that explicitly list modifications, creations, and deletions while detailing the testing strategies for your software architecture.