design-architecture

# Design Architecture Skill This skill performs a structured architecture review by dispatching four specialist subagents in parallel, then consolidating their findings into a maintained `architecture.md` document. One of the four subagents is a dedicated adversarial red-team agent that probes failure paths, invariant bypasses, and silent corruption scenarios that the structural review agents would not naturally surface. The goal is not to produce a one-time report — it's to maintain a living architectural record that evolves as the codebase evolves. The to-do list inside `architecture.md` becomes the actionable roadmap. --- ## Workflow ### Step 1 — Read existing architecture.md (if it exists) Before spawning subagents, check whether `architecture.md` already exists in the project root. If it does, read it so you understand what was previously documented, what to-dos are already tracked, and what changes have already been logged. This context shapes what the subagents should focus on (new ground vs. follow-up on prior findings). ### Step 2 — Spawn four subagents in parallel Launch all four at once (same message, parallel Agent tool calls). Each subagent is defined in `.claude/agents/` — use the `subagent_type` parameter to route to each one: | Subagent | File | `subagent_type` | Lens | |----------|------|-----------------|------| | System Architect | `.claude/agents/system-architect.md` | `system-architect` | Pipeline structure, orchestration, re-entry | | Software A...