Cohesive Clean Breaks

Use this skill when a coding decision changes public shape, package boundaries, runtime contracts, naming, config structure, lifecycle ownership, or migration strategy.

The goal is not to minimize diff size. The goal is to make the final system easy to explain, hard to misuse, and free of half-old, half-new behavior.

Related skills: use one-sentence-test to state the thesis, refactoring for caller counting and straggler sweeps, approachability-audit for first-read clarity, change-proposal when showing current and proposed trees before editing, and post-implementation-review after implementation.

References