What problem does it solve? Architecture reviews often happen only after something breaks, or degrade into gut-feel judgments. This Skill turns architecture review into a routine checkpoint by forcing a complete read of ARCHITECTURE_DESIGN.md (all sections and ADRs) before any assessment, then evaluating changes against 8 defined dimensions. ## Core Features & Use Cases - Story Review (Mode A): Evaluates a single story or planned change against relevant architecture dimensions before implementation, producing per-dimension status (OK / Warning / Critical), findings, and recommendations. - System Review (Mode B): Audits the entire system across all 8 dimensions, identifying strengths, top risks, tech debt level, and recommended backlog issues. - Enforced documentation checklist: Requires reading sections 1-8 and every ADR of the architecture design document before judging, tying every finding to a concrete design decision. - Use Case: Before sending a story about a new Kafka consumer retry mechanism to implementation, run a Story Review to catch missing exponential backoff and get a concrete recommendation referencing existing ADR precedents. ## Quick Start Ask the assistant to run an architecture review on the current story by saying "/architecture-review" or "does this change fit architecturally?".