architecture-reviewlisted

# Architecture Review When this skill is activated, perform a structured architecture review of a feature, module, or the full codebase and produce a `docs/reviews/ARCHITECTURE_REVIEW.md` report. This review evaluates the *quality* of the architecture as built — not the original intent. ## Clarifying Questions Before starting the review, ask the engineer the following questions. Skip any already clearly answered in the conversation. **Wait for the answers before proceeding.** 1. What is the scope — a specific module or feature, or the full codebase? 2. What is the goal of this review? (e.g. pre-release sanity check, before a major refactor, understanding current state, identifying technical debt) 3. Are there specific dimensions or concerns you want focused on — e.g. dependency direction, testability, layer separation? 4. Are there known problem areas you already suspect? Where does the code feel wrong to you? 5. Does a `docs/DESIGN.md` or `docs/SYSTEM_DESIGN.md` exist that the implementation should be compared against? ## Steps 1. Use the answers above to set scope and focus; fall back to full codebase only if scope was not specified 2. Explore the directory and file structure to understand module boundaries 3. Read the key source files — focus on entry points, core domain logic, and infrastructure integrations 4. Evaluate the architecture against each dimension below 5. Identify violations with specific evidence (file path + line numbers) 6. Recommend concrete improve