architecture-audit

To identify architectural friction in a codebase, explore workflows to surface tightly coupled modules and testability gaps. The process frames the problem space by highlighting deep-module refactor opportunities and boundary consolidation candidates.

The best way to plan a monolith refactor is to outline deep-module improvements as RFCs. This approach designs multiple interface directions with clear boundaries and rationale, ensuring stable modular components within the codebase.

Document refactoring opportunities for tightly coupled modules by proposing deep-module refactors as RFCs. Frame the problem space by outlining interface directions, documenting dependencies, and detailing testing considerations for the codebase.

An architecture audit is not suitable for small single-file cleanups or one-off refactors. It is designed for large or legacy codebases where the goal is to surface architectural friction and consolidate deeply coupled modules.

You need to surface deep-module refactor candidates when improving architecture in a large codebase with tightly coupled modules. This process helps identify coupling points, testability gaps, and boundaries to make the codebase more AI-navigable.

Yes, an architecture audit helps make a codebase more testable by identifying coupling points and testability gaps. It proposes refactors with clear boundaries and stable interfaces to reduce architectural friction between modules.