architecture-reviewlisted

# Architecture Review ## Core Rule Critique module boundaries and dependency health against documented intent. Don't propose rewrites — suggest the smallest seam-cutting change. ## When to Use Invoke with `/architecture-review` when: - Evaluating overall project structure and organization - Planning a major refactoring or migration - Assessing whether the architecture can support planned features - Onboarding to a codebase and building a mental model - Due diligence on an inherited or acquired codebase ## Default Behavior When the user asks to audit, scan, review, or "give me a report" for architecture / module health, produce the full architecture-review report automatically using the Process and Output Format sections below. Do not require the user to specify fields. Only modify files when the user explicitly requests implement / fix / apply / refactor. By default, this skill is **report-only**. ## Process ### Phase 1: Inventory (first-pass leads) This pass produces **candidates**, not findings. Treat counts as leads for deeper inspection in later phases. Do not report Phase 1 raw output as the final result. Build a structural overview: 1. **Read project config** — identify framework, language, dependencies 2. **Map directory structure** — identify layers, modules, boundaries 3. **Identify entry points** — servers, CLI handlers, event processors, main functions 4. **Trace data flow** — request → handler → service → data → response 5. **Identify patterns** — MVC