architecture-designlisted

# Architecture Design (System Level) Produce system-level architecture decisions: bounded contexts, module boundaries, layering, dependency flow. Output ADRs and diagrams only when they add value. ## Scope **In scope:** domains, bounded contexts, modules, layers, dependency direction, integration boundaries, data ownership, cross-cutting concerns (auth, logging, events). **Out of scope:** class structure, method signatures, design patterns inside a module (→ `component-design`), feature requirements or user stories, code-level bugs. ## Examples ```bash # Design architecture for a new subsystem /architecture-design order fulfillment module # Design architecture for the whole project (exploratory) /architecture-design ``` ## Workflow ```mermaid flowchart TD A["Load project context"] --> B["Detect stack & conventions"] B --> C["Research best practices"] C --> D["Clarify scope with user"] D --> E["Propose 2-3 approaches"] E --> F["User picks approach"] F --> G["Draft structural design"] G --> H["Write ADR if decision is non-obvious"] H --> I["Summarize + next steps"] ``` ## Phase 1: Load Project Context Check in order, stop at first hit: 1. `.agent-context/layer1-bootstrap.md` → tech stack, project identity 2. `.agent-context/layer2-project-core.md` → conventions, critical rules 3. `.agent-context/decisions.json` → existing architectural decisions (ADRs) 4. `CLAUDE.md`, `AGENTS.md`, `CONTRIBUTING.md`, `README.md` 5. Manifest files: `composer.json`, `pa