Surveys a real repository for structural problems and turns the findings into a staged plan: measures churn, size, import cycles, coupling and co-change, finds shallow modules (wrappers that hide nothing) and tangled clusters, ranks a few candidates on evidence, designs the new boundary and proposes the change as small reversible steps guarded by a CI rule. Use when someone says "improve the architecture", "where should we refactor", "this codebase is a mess", "find the worst modules", "untangle these dependencies", "too many tiny files", "make this easier to test", or asks for a refactoring roadmap.
