improve-codebase-architecture

To identify shallow modules and seams hindering testability, analyze your domain glossary and ADRs. You can then apply a deletion test to candidate modules to surface architectural friction and propose deepening opportunities with clear rationale.

The deletion test evaluates module architecture by checking candidate modules for shallow integration. It surfaces deepening opportunities by identifying seams that block testability, helping prioritize refactor changes without creating new interfaces initially.

Improve AI-navigability by exploring CONTEXT.md and ADRs to find architectural friction. Propose structured deepening candidates listing affected files, problems, solutions, and benefits to enhance both testability and AI codebase navigation.

Refactor architectural seams when shallow modules block testing and AI navigation. Use a grilling loop to refine constraints against ADR considerations, documenting prioritized changes in CONTEXT.md terminology before implementing new interfaces.

Yes, you can propose architecture deepening opportunities without creating new interfaces. The process surfaces a prioritized list of changes documenting affected files, rationale, and ADR alignment, deferring interface creation to later stages.

Document architectural friction by aligning with CONTEXT.md terminology and ADRs. Present a prioritized list of deepening candidates including affected modules, problems, solutions, and benefits to ensure team alignment on testability improvements.