verify-design-a

To review code architecture, evaluate module structure, dependencies, and abstractions to surface misdesigns and unnecessary complexity. This process identifies weak design choices and unsuitable abstractions that hinder maintainability, justifying refactoring decisions.

Perform an architecture review when evaluating code in hindsight to find misdesigns and unnecessary complexity. It is needed when module structure, dependencies, or layer boundaries show coupling or weak abstractions that hinder maintainability and require targeted refactors.

The best way to document code review findings is using a structured format including observations, questions, alternatives, and impacts. This guides refactors by evaluating type and design fit, module structure, and dependencies to justify architectural choices.

Prioritize refactoring candidates by generating FROM/TO/TRADEOFF lists from dependency analysis. This targets improvements by evaluating module dependencies and layer boundaries, providing structured observations and impacts to guide your refactoring decisions.

Yes, architectural review applies to scenarios across modules, dependencies, and layer boundaries. It evaluates design fit and abstractions to surface coupling and unnecessary complexity, guiding refactor candidacy with structured observations, questions, alternatives, and impacts.