rai-architecture-review

Detect over-engineering by auditing implemented code for necessity and proportionality using Beck's four rules, checking for unused parameters, dead exports, and wrapper layers without logic against the original design intent.

A YAGNI necessity audit identifies speculative work by finding single implementations, wrappers without logic, unused parameters, test-only consumers, and dead exports to prevent gold-plating in the codebase.

Perform a post-implementation architecture review by loading the design document, analyzing git diffs of changed files, and evaluating established patterns across project modules to produce heuristic-tagged findings and a PASS or SIMPLIFY verdict.

Yes, you need design documents, git diffs, project language detection, and access to the knowledge graph to evaluate design proportionality and measure the abstraction-to-LOC ratio accurately.

Identify systemic issues by running an epic-scope architecture review to detect orphaned abstractions, coupling direction issues, cyclic dependencies, and shotgun surgery across project modules to ensure lean compliance.

Run a design proportionality audit after a story implementation to verify minimal correct design, at epic close for cross-module systemic issues, or on-demand when complexity feels disproportionate to the design intent.