arch-refactor

Document an architectural refactor using ADRs by drafting Architecture Decision Records that capture structural changes to module boundaries and orchestration, ensuring traceability across discussion, planning, and implementation phases.

A phased workflow for software architecture refactoring enforces hard exit gates between discussion, ADR drafting, planning, and implementation, coordinating sub-agents at each step to maintain structural integrity and documentation.

You need an Architecture Decision Record for a code modularization when major structural changes affect module boundaries, introduce pluggable protocols, or extract abstractions, requiring gated documentation and traceability.

Plan structural changes affecting module boundaries and orchestration by enforcing a phased execution workflow with explicit gates, coordinating ADRs and sub-agent dispatch to guide discussion, ADR drafting, and implementation planning.

Yes, you can use paired ADRs for splitting classes along conceptual lines to ensure traceability, coordinating documentation and phased implementation when introducing protocols or pluggable boundaries during the refactor.

Gated architectural refactoring workflows require strict adherence to exit gates between discussion, ADR, plan, and implementation phases, which may introduce overhead for minor structural changes that do not affect module boundaries or extensibility.