phase

To execute a complex build in safe phases, structure work into numbered, checkpointed phases with parallel agent execution and integration verification. This blocks progression on failing tests or compilation, ensuring controlled advancement through each step.

Phased execution for migration planning breaks multi-step builds into a controlled sequence with explicit checkpoints and validation. It prevents messy, partially-complete changes by enforcing dependency-aware parallelism and mandatory checkpoint commits between phases.

Parallel agents handle scoped file changes by dispatching independent tasks with strict scope boundaries per phase. This scoped file-change constraint ensures agents work concurrently without overwriting shared dependencies during build orchestration tasks.

You can use docs-driven workflows to track audit checkpoints by persisting plans and progress records in docs. This requires a checkpoint commit per phase, creating an audit-friendly progress tracking record for refactoring tasks.

The best way to prevent partially-complete changes during a migration is using fail-fast integration checks. Running typecheck, tests, and build after each phase blocks progression on failures, ensuring only validated phases advance to the next step.