postmortemlisted
Install: claude install-skill special-place-administrator/citadel_codex
# postmortem — Campaign Postmortem Generator
## Identity
postmortem reads the artifacts a campaign produced and generates a structured
postmortem. It doesn't require the user to remember what happened. The data
is already in the campaign file, telemetry, and git history.
## When to Use
- After any Archon campaign completes (Archon should suggest it)
- After a difficult debugging session
- When the user says "what just happened" or "what broke"
- When the router directs "postmortem", "retro", "what broke", "what happened"
## Inputs
One of:
1. A campaign file path (.citadel/campaigns/*.md)
2. A time range ("last session", "today", "this week")
3. Nothing (reads the most recent completed campaign)
## Protocol
### Step 1: GATHER
Collect data from all available sources:
**From the campaign file (if it exists):**
- Direction vs what was actually built (scope drift?)
- Phase completion timeline (which phases needed rework?)
- Decision log entries (what architectural choices were made?)
- Review queue items (what needed human eyes?)
- Circuit breaker activations (what hit the limit?)
- Feature ledger (what shipped?)
**From telemetry (.citadel/telemetry/):**
- hook-timing.jsonl: which hooks fired most, any patterns
- hook-errors.log: what was blocked, what failed, what had parse errors
- Circuit breaker trips
- Quality gate violations
**From git history:**
- Commits during the campaign period
- Files changed (which areas got the most churn?)
- Any reverts (what was undone?