Safe migration plan
A step-by-step plan for a schema, framework or data migration with zero downtime and a rollback at each step.
Use it when
Changing something in production that users depend on.
What you fill in
- change What is changing, from what to what
- system Traffic, data size, deploy process
The prompt
Plan this migration: change. System: system. Give numbered steps using expand-and-contract where it applies. For each step: what changes, how to verify it worked, how to roll back, and whether it can run during traffic. Include backfill strategy and size estimate, monitoring to watch, the point of no return (if any), and a pre-flight checklist. Before you answer, check your draft against every instruction above and fix anything that misses.
Why it works
- Expand-and-contract avoids downtime.
- Verification and rollback per step.
- Names the point of no return explicitly.