improve-codebase-architecture

Codebase architecture deepening opportunities are identified by analyzing modules for shallow interfaces and friction points. The tool reads domain vocabulary and ADR decisions to surface concrete candidates with problem, solution, and benefits for design review.

Refactoring tightly-coupled modules requires surfacing shallow interfaces and proposing seams with adapters. This tool analyzes domain glossaries and architecture decisions to output a prioritized list of impacted files and rationale for improving testability and AI-navigability.

To find shallow modules, the tool reads CONTEXT.md for domain vocabulary and ADRs to identify friction points between modules. It then proposes deepening candidates with locality and leverage considerations to align refactoring with existing architecture decisions.

Yes, you can refine architecture refactoring candidates interactively. The tool features a grilling loop that uses documentation to challenge and refine proposed deepening opportunities, ensuring they maintain alignment with your ADR decisions during design review.

A deepening candidate output for codebase modularity includes the problem, solution, and benefits. It provides a prioritized list featuring specific files, impacted modules, identified seams and adapters, and rationale suitable for design review.

Automated deepening analysis requires existing CONTEXT.md and ADR documentation to function effectively. You should not use it if your codebase lacks a domain glossary or architecture decision records, as the tool relies on these to identify friction points and propose refactoring candidates.