Prompt library
Outline a zero-drama migration plan
Expand/contract phasing with explicit entry/exit criteria is the pattern that removes the big-bang moment where migrations die. Requiring a measured agreement threshold before cutover replaces confidence with evidence, and the rollback rule bans the steps that cause resume-generating events.
Last reviewed July 17, 2026
The prompt
Outline a migration plan.
What is migrating and why: {{migration}}
Constraints: {{constraints}}
Produce:
1. End state and the measurable definition of "migration complete".
2. Phases in expand/contract shape: expand (new path exists, old still authoritative), verify (both run, diffs measured), cutover (new authoritative, old readable), contract (old removed). For each phase: entry criteria, exit criteria, and rollback procedure.
3. The diff harness: how we prove old and new agree before cutover (shadow reads, dual writes, checksums), and the agreement threshold that permits cutover.
4. Blast-radius controls: how cutover is staged (by tenant, percentage, region) and the abort trigger per stage.
5. The long tail: data or callers that will resist; how each is detected and handled.
6. A one-line status format the team posts at each phase boundary.
Never plan a step whose rollback is "restore from backup and apologize".Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{migration}} | What moves where, and the driver | user sessions from a single Redis to a clustered setup |
| {{constraints}} | Downtime tolerance, team size, deadline | no planned downtime, 2 engineers, 6 weeks |