mp-architecture-review

To identify architectural friction and turn it into a refactor RFC, analyze the codebase for tightly coupled seams and testability gaps, then convert those deepening opportunities into an actionable GitHub RFC issue using a repository template.

You need deep modules for interface design refactoring when your current interfaces are shallow, tightly coupled, or hard to test. Deepening these modules improves dependency handling and increases overall system maintainability.

To plan boundary-level tests for tightly coupled code, classify dependencies into categories like in-process, local-substitutable, and ports and adapters. This strategy replaces brittle shallow-module tests with safer interface-boundary tests.

The best way to untangle tightly coupled dependencies using ports and adapters is to classify dependencies by category and design radically different interface options. This frames clear deepening opportunities for your refactor proposal.

Yes, you can generate a GitHub RFC issue directly from your architecture review. The process produces an issue body using your repository's specific RFC template, making the deep-module refactor plan ready for immediate implementation.

Yes, dependency-category-based planning works for any software codebase by classifying dependencies into in-process, local-substitutable, ports and adapters, and true external categories to drive the appropriate refactor and testing strategy.