improve-codebase-architecture

To identify shallow modules, scan the codebase for interfaces that expose too much implementation detail or lack stable seams. This reveals architectural friction where understanding behavior requires bouncing across many modules.

Improve codebase architecture by finding shallow modules and proposing deepening refactors that increase leverage at module interfaces. This approach enhances testability by ensuring tests verify behavior through stable seams.

Fix leaky seams by surfacing deepening opportunities with clear candidates that frame benefits as locality and leverage. You then grill a chosen candidate to converge on safe refactoring decisions and deep module boundaries.

Redesign module interfaces when deepening a shallow module requires alternative designs. A grilling loop crystallizes the design and uses parallel sub-agent exploration to propose optional interface redesigns.

Yes, architectural refactoring requires an exploration phase to scan the codebase and note missing seams. This precedes a candidate-listing phase that defines the problem, proposed change, and locality benefits.