Program Cutover Plan

---
name: program-cutover-plan
description: Coordinate a multi-system or multi-team cutover with prerequisites, freeze points, migration sequence, communication, command roles, rollback/forward recovery, and post-cutover validation.
---
# Program Cutover Plan

Use when this procedure is the primary professional method needed for the assignment.

## Procedure
1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using release/migration plans, dependencies, rollback procedures, support/on-call, data compatibility, and stakeholder windows. Do not fill material gaps with assumptions when they can change the result.
3. Build minute/order-level dependency sequence where needed, define no-go criteria and authority, rehearse critical steps, synchronize communications, and validate end state.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

## Quality gate
The cutover can be stopped or recovered safely and completion is declared only from integrated evidence.