postmortem

1# /postmortem — Campaign Postmortem Generator
2 
3## Orientation
4 
5**Use when:** A campaign just completed and you want a structured analysis of what broke, what safety systems caught, and what patterns emerged. Also for ad-hoc incident analysis from recent git history.
6 
7**Don't use when:** You want to preserve session context for the next conversation (use `/session-handoff`), extract reusable patterns from findings into the knowledge base (use `/learn`), or score and improve quality iteratively (use `/improve`).
8 
9## When to Use
10 
11- After any Archon campaign completes (Archon should suggest it)
12- After a difficult debugging session
13- When the user says "what just happened" or "what broke"
14- When /do routes "postmortem", "retro", "what broke", "what happened"
15 
16## Inputs
17 
18One of:
191. A campaign file path (.planning/campaigns/*.md)
202. A time range ("last session", "today", "this week")
213. Nothing (reads the most recent completed campaign)
22 
23## Protocol
24 
25### Step 1: GATHER
26 
27Collect data from all available sources:
28 
29**From the campaign file (if it exists):**
30- Direction vs what was actually built (scope drift?)
31- Phase completion timeline (which phases needed rework?)
32- Decision log entries (what architectural choices were made?)
33- Review queue items (what needed human eyes?)
34- Circuit breaker activations (what hit the limit?)
35- Feature ledger (what shipped?)
36 
37**From telemetry (.planning/telemetry/):**
38- hook-timing.jsonl: which hooks fired most, any patterns
39…