go-modularize
Go Modularize
A seven-phase workflow for finding the right Go module boundaries — splitting a monolith into semi-independent sub-modules, merging over-split modules, or refining existing boundaries. Each module gets its own go.mod. The process detects the current state, proposes boundaries, subjects the proposal to brutal self-review, plans execution with Pareto prioritization, executes step by step, and closes with a reflection ensuring the result is superb and long-lasting.
Load ./references/phases.md for the detailed phase procedures. This file contains the decision framework, failure modes, and tooling reference needed before and during execution. For a worked before/after example, see ./references/example.md. For patterns distilled from production Go multi-module projects (dual go.work+replace strategy, CI verification, error architecture, test infrastructure), see ./references/real-world-patterns.md.