data-migration-runbook-author

What problem does it solve?

It turns an approved data-move plan into a clear operator runbook so a stranger can execute a backfill, re-shard, cutover, tenant move, or CDC initial load without improvising under pressure.

Core Features & Use Cases

• Prerequisite gating: Requires an approved plan, safety review verdict, and verified backup evidence before any execution steps are written.
• Operator-safe batching and verification: Defines batch sizing, throttling, pause/resume behavior, per-batch parity checks, and full-keyspace validation with explicit expected outputs.
• Abort and rollback discipline: Specifies numeric abort thresholds, named safe-halt states, stage-by-stage rollback steps, and human approval markers for destructive or irreversible actions.
• Use case: A team approves an orders backfill and needs a runbook that states how to batch it, verify it, halt safely on lag or parity issues, and switch back if post-cutover errors rise.

Quick Start

Ask for an operator-executable runbook for the approved data move, including prerequisites, batching, verification, abort criteria, rollback, and approval gates.