architecture-design

Generate and validate Solution Design Documents against PRD requirements.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill architecture-design-i2oland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-design
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/architecture-design
Command: npx skills add https://github.com/I2olanD/dotfiles --skill architecture-design-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture design and documentation are often scattered across sources, leading to misalignment and incomplete specs. This Skill provides a structured approach to create and validate Solution Design Documents (SDDs), ensuring architecture decisions are clear, traceable, and aligned with PRD requirements.

Core Features & Use Cases

  • Template-driven SDD creation: Generates a complete SDD scaffold from the template.
  • Section-level guidance: Focuses on HOW the solution will be built, where code and interfaces reside, and the rationale behind decisions.
  • Validation & ADR support: Includes validation steps, consistency checks, and ADR documentation for key decisions.
  • Use Case: When starting a new system or major component, create docs/specs/[NNN]-[name]/solution-design.md that adheres to the template, ensuring completeness and traceability.

Quick Start

Activate the skill and create an SDD by following the template steps:

  1. Read the template at ~/.config/opencode/skill/solution-design/template.md
  2. Write your spec to docs/specs/[NNN]-[name]/solution-design.md
  3. Run the validation workflow to confirm alignment with PRD requirements and ADRs.

Frequently Asked Questions about architecture-design

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

FAQPage Schema
How do I create a solution design document for a new software architecture?▼

Create a solution design document by reading the SDD template and writing your spec to docs/specs/[NNN]-[name]/solution-design.md. This generates a complete scaffold covering component boundaries, interfaces, and deployment considerations for your architecture.

What is a solution design document and when do I need one for my project?▼

A solution design document (SDD) defines how a system will be built, including architecture patterns, component boundaries, and rationale. You need an SDD when starting a new system or major component to ensure decisions are traceable and aligned with PRD requirements.

How do I validate my architecture design against PRD requirements?▼

Validate your architecture design by running the validation workflow to confirm alignment with PRD requirements and ADRs. This performs consistency checks on the solution-design.md file to ensure complete traceability across your architecture decisions.

Can I use this approach to document architecture decisions for complex systems?▼

Yes, this approach supports complex systems by enforcing complete, traceable design through ADR documentation and section-level guidance. It guides architecture patterns, component boundaries, and deployment considerations for scalable software architectures.

Why does my architecture documentation lack traceability across components?▼

Architecture documentation lacks traceability when scattered across sources without a structured template. Using a solution design document enforces clear, traceable decisions aligned with PRD requirements through validation steps and ADR documentation.

What's the best way to structure architecture patterns and component boundaries in specs?▼

The best way to structure architecture patterns is using a template-driven SDD that provides section-level guidance on component boundaries, interfaces, and ADRs. This ensures completeness and traceability in your docs/specs/ directory.