Structure a Postmortem Report
Added 2026-10
Structure a Postmortem Report — Chinese original prompt
请根据 [故障经过与日志]，写一份复盘报告：影响范围与持续时间、按分钟的时间线、直接原因与根本原因的区别、处置过程中哪些判断是对的哪些走了弯路，以及可落地的改进项。输出：报告正文、改进项清单（负责人、截止时间、验收标准）、需要同步给客户的说明口径。
Site original
Chinese original
Example
Sample input
故障经过和日志在下面，是一次支付回调堆积，持续四十分钟，帮我写复盘报告。
The output should include
- 影响范围与分钟级时间线写清
- 直接原因与根本原因分开写
- 改进项带负责人截止与验收
Replace these placeholders 1
Swap the bracketed parts for your own details before sending.
[故障经过与日志]
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.