architecture-designlisted

# architecture-design ## Purpose Guide the design of a system or feature from requirements to a documented architecture. Produces C4-model diagrams (Context → Container → Component), service boundary definitions, API contracts, data flow diagrams, failure mode analysis, and an ADR for the key decisions made. Works standalone or as the `/abd-design` agent in the ABD workflow. **Quick mode** (`/architecture-design --quick`): for single-feature or small-scope designs. Skip Step 5 (C4 Level 3), make the Step 8 failure-mode table optional (include only externally-dependent paths), and keep Steps 1–2 to a single confirmation exchange. **Emit as you go:** output each step's section immediately as you complete it rather than composing the whole document at the end. Step 10 assembles the already-emitted sections into the saved file. This keeps quality even across sections. --- ## Instructions ### Step 1 — Gather inputs Ask the user for (or read from existing artifacts): - What are we building? (description or link to requirements doc / Jira epic) - What are the key constraints? (team size, existing systems to integrate with, cloud provider, language preference, compliance requirements) - What is the expected scale? (users/day, requests/second, data volume) - What is the timeline? (affects how complex a solution is appropriate) - Are there existing systems this must integrate with or replace? If `docs/requirements/` exists, use Glob and Read to load relevant requirements docum