refactoring-workflow

Automated refactoring checks enforce a 3-Phase compliance strategy to ensure safe code migration. The workflow validates the 5-step execution order across Infrastructure, Client, and Server layers, guaranteeing new pattern implementation, test additions, compatibility checks, staged migration, and old code removal.

The 3-Phase Refactoring workflow is a staged migration strategy that safely removes legacy code by enforcing a strict 5-step execution order. It validates pattern implementation, test additions, compatibility checks, staged migration, and old code removal across Infrastructure, Client, and Server layers for auditable outcomes.

You can enforce a refactoring plan order by reading and applying rules from CLAUDE.md and docs/REFACTORING_PLAN.md. The workflow integrates with phase checkers under the agents/ directory to deterministically verify that your codebase follows the standard 5-step execution sequence.

Yes, the automated refactoring workflow applies across Infrastructure, Client, and Server layers. It enforces phase order and the 5-step execution sequence to ensure compatibility checks and staged migration are validated deterministically across all three architectural layers.

Staged migration fails the phase check when the 5-step execution order is violated. The workflow enforces sequential compliance for new pattern implementation, test additions, compatibility checks, staged migration, and old code removal to guarantee safe migrations without breaking existing functionality.