improve-branch-architecture
Improve Branch Architecture
Surface architectural friction and propose deepening opportunities — refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability.
This skill is the branch-scoped sibling of improve-codebase-architecture. It runs that skill's entire approach — the same three phases, the same vocabulary, the same deepening discipline, the same inline CONTEXT.md/ADR side effects — changed in exactly two ways:
- Scope is the current branch's changes plus the foldable radius, not the whole codebase.
- Medium is in-conversation markdown with ASCII before→after sketches, not a self-contained HTML report.
For a whole-codebase audit, use improve-codebase-architecture. For a correctness/bug review of the branch, use review-code.
Vocabulary
Every suggestion uses the deep-module vocabulary — module, interface, depth (deep/shallow), seam, adapter, leverage, locality. Use these terms exactly; don't drift into "component," "service," "API," or "boundary." Full definitions and principles are in LANGUAGE.md — read it before writing suggestions if any term above is unfamiliar.
The principle the Process below leans on hardest is the deletion test: imagine deleting the module — if complexity vanishes it was a pass-through, if complexity reappears across N callers it was earning its keep.
This skill is informed by the project's domain model. The domain language gives names to good seams; ADRs record decisions the skill should not re-litigate.