implement-refactor

End-to-end code migration is orchestrated by sequentially applying phase-based transformations, locking in current behavior with characterization tests, and generating a final decisions log. This ensures changes are applied safely across dependency waves with continuous review.

The best way to safely refactor architecture is executing tasks in dependency order across multiple waves. Safety checks keep tests green during phase-based transformation, while spawned reviewers apply fixes to enforce disciplined, auditable migrations.

Characterization tests preserve existing behavior during a code refactor by reading the agreed architecture and requirements, then generating and running tests that verify current functionality is maintained before transformations are applied.

Yes, an agreed architecture, mapped dependencies, and defined artifacts are required before starting. The orchestrator enforces this prerequisite to apply disciplined transformations, satisfy test locks, and support safe, auditable migrations.

Code refactoring decisions are logged and documented for auditability by spawning a review cycle that produces a comprehensive summary and decisions log. Finalizing changes updates the refactor index and communicates outcomes.

Use an automated refactor orchestrator instead of manual code migration when your task spans multiple phases, waves, and iterations. It enforces required test locks, change propagation, and decision logging that manual migrations often miss.