Prepare a Rollback Plan for a Release
Added 2026-10-31
Define rollback triggers, steps and verification before shipping, not during an incident.
We are shipping a change. I will give scope, affected users and external dependencies. Produce a rollback plan: 1) three must-rollback triggers as observable signals; 2) concrete steps including data compatibility; 3) how to verify recovery afterwards; 4) changes that cannot be rolled back once shipped and need gradual rollout or flags. Output as a checklist, keep it short.
Site original
Chinese original
How to use
回滚方案要在发布前写，不是出事时编。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.