Write a Runbook for a Recurring Incident
Added 2026-11-03
Turn how we fixed it last time into steps anyone can follow.
We have a recurring incident (history below). Write a runbook: 1) typical symptoms and how to confirm it is this incident; 2) the first three stop-the-bleeding actions, who does them and how fast; 3) how to confirm recovery; 4) the order for root-cause investigation; 5) when to escalate and to whom; 6) what must be recorded afterwards. Every step must be an action, not "check it".
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.