Back to Details

postmortem

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

description: Create blameless postmortem from the incident we just resolved argument-hint: [optional: additional context or specific focus]

description: 基于刚解决的事件创建无责事后复盘报告 argument-hint: [可选：额外上下文或特定重点]

POSTMORTEM

事后复盘报告

Generate a blameless postmortem from this conversation.
You just helped resolve an incident. The investigation context, hypotheses, evidence, and fix are all in this conversation (and likely in an INCIDENT.md file).
基于本次对话生成一份无责事后复盘报告。
你刚刚协助解决了一起事件。调查背景、假设、证据以及修复方案均包含在本次对话中（也可能存在于INCIDENT.md文件内）。

Output Structure

输出结构

Write a postmortem with:
  • Summary: One paragraph - what happened, impact, resolution
  • Timeline: Key events in UTC (use conversation timestamps if available)
  • Root Cause: The actual underlying cause (not symptoms)
  • 5 Whys: Dig to systemic factors
  • What Went Well: Recognition of good practices during response
  • What Went Wrong: Honest assessment without blame
  • Follow-up Actions: Concrete items with clear ownership
撰写复盘报告时需包含以下部分：
  • 摘要：一段内容 - 事件经过、影响范围、解决结果
  • 时间线：UTC时区的关键事件（若有对话时间戳则使用该时间戳）
  • 根本原因：实际的底层原因（而非表面症状）
  • 5个为什么：深挖系统性因素
  • 做得好的地方：认可响应过程中的良好实践
  • 待改进之处：坦诚评估，不涉及指责
  • 跟进行动：明确责任人的具体事项

Philosophy

原则

  • Blameless: Focus on systems, processes, and tools - not people
  • Honest: Don't minimize or exaggerate
  • Actionable: Every lesson should have a concrete follow-up
If INCIDENT.md exists, update its postmortem section. Otherwise create POSTMORTEM-{timestamp}.md.
Optional focus: $ARGUMENTS
  • 无责：聚焦于系统、流程与工具 - 而非个人
  • 坦诚：不刻意淡化或夸大事实
  • 可落地：每个经验教训都需对应具体的跟进事项
若存在INCIDENT.md文件，请更新其中的事后复盘部分。否则创建POSTMORTEM-{timestamp}.md文件。
可选重点：$ARGUMENTS