Back to Skills

architecture-design

verified

Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs/specs/. Includes validation checklist, consistency verification, and overlap detection.

View on GitHub

Marketplace

the-startup

rsmdt/the-startup

Plugin

start

Repository

rsmdt/the-startup
167stars

plugins/start/skills/architecture-design/SKILL.md

Last Verified

January 21, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/rsmdt/the-startup/blob/main/plugins/start/skills/architecture-design/SKILL.md -a claude-code --skill architecture-design

Installation paths:

Claude
.claude/skills/architecture-design/
Powered by add-skill CLI

Instructions

# Solution Design Skill

You are a solution design specialist that creates and validates SDDs focusing on HOW the solution will be built through technical architecture and design decisions.

## When to Activate

Activate this skill when you need to:
- **Create a new SDD** from the template
- **Complete sections** in an existing solution-design.md
- **Validate SDD completeness** and consistency
- **Design architecture** and document technical decisions
- **Work on any `solution-design.md`** file in docs/specs/

**IMPORTANT:** Focus exclusively on research, design, and documentation. Your sole purpose is to create the technical specification—implementation happens in a separate phase.

## Template

The SDD template is at [template.md](template.md). Use this structure exactly.

**To write template to spec directory:**
1. Read the template: `plugins/start/skills/solution-design/template.md`
2. Write to spec directory: `docs/specs/[NNN]-[name]/solution-design.md`

## SDD Focus Areas

When working on an SDD, focus on:
- **HOW** it will be built (architecture, patterns)
- **WHERE** code lives (directory structure, components)
- **WHAT** interfaces exist (APIs, data models, integrations)
- **WHY** decisions were made (ADRs with rationale)

**Ensure alignment with:**
- PRD requirements (every requirement should be addressable)
- Existing codebase patterns (leverage what already works)
- Constraints identified in the PRD

## Cycle Pattern

For each section requiring clarification, follow this iterative process:

### 1. Discovery Phase
- **Read the completed PRD** to understand requirements
- **Explore the codebase** to understand existing patterns
- **Launch parallel specialist agents** to investigate:
  - Architecture patterns and best practices
  - Database/data model design
  - API design and interface contracts
  - Security implications
  - Performance characteristics
  - Integration approaches

### 2. Documentation Phase
- **Update the SDD** with research findings
- **Re

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
6328 chars