rb-architecture-review

To identify architectural risks, perform a structural critique that maps dependencies, detects circular references, and evaluates module boundaries. This process highlights shallow modules and poor test seams that hinder maintainability.

The best way to assess technical debt before scaling is conducting a systematic structural analysis to prioritize risks based on impact and likelihood. This reveals hidden boundaries and coupling problems that prevent new feature implementation.

To generate a prioritized refactoring plan for poor software design, analyze the repository structure to pinpoint shallow modules and circular dependencies. This yields a strategy targeting the most critical structural decay first.

You need an architecture review when preparing to scale a system or suspecting current coupling prevents new feature implementation. It evaluates modularity, maps dependencies, and checks if state machines and orchestration layers are necessary.

A structural critique requires adherence to established project conventions while evaluating the codebase. It systematically assesses modularity and dependency mapping without overriding your existing software design standards.

Hidden technical debt makes refactoring difficult because unclear boundaries and structural decay obscure coupling issues. A systematic architecture review exposes these shallow modules and poor test seams to create a clear improvement strategy.