메뉴
Blameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | postmortem |
| description | Blameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring. |
| user-invocable | true |
Conduct a thorough, blameless analysis of an incident to understand what happened and prevent recurrence.
Work through each section systematically. Focus on systems and processes, not individuals. The goal is learning, not blame.
Incident: [One-line description] Date/Time: [When it occurred] Duration: [How long] Severity: [Critical/High/Medium/Low]
Summary [2-3 sentence overview: what happened, impact, resolution]
All times in [timezone].
| Time | Event | Actor |
|---|---|---|
| HH:MM | [What happened] | [Who/what did it] |
| HH:MM | [Detection] | [How it was noticed] |
| HH:MM | [Response action] | [Who responded] |
| HH:MM | [Resolution] | [What fixed it] |
Key Moments
Customer Impact
Business Impact
Root Cause [The fundamental reason this happened—not the trigger, but why the trigger caused an incident]
Trigger [The immediate cause—what set things in motion]
Contributing Factors
| Factor | How It Contributed |
|---|---|
| [factor] | [explanation] |
Why Wasn't This Caught?
| What Worked | Why It Helped |
|---|---|
| [thing] | [explanation] |
| What Failed | Impact |
|---|---|
| [thing] | [impact] |
Immediate (This week)
| Action | Owner | Due |
|---|---|---|
| [action] | [owner] | [date] |
Short-term (This month)
| Action | Owner | Due |
|---|---|---|
| [action] | [owner] | [date] |
$ARGUMENTS
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V. Use when editing prose, reviewing drafts, or improving writing clarity and tone.
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.
After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.
Cynefin sense-making framework categorizing problems as Simple, Complicated, Complex, Chaotic, or Confused to select the right approach. Use when unsure how to tackle a problem.
