postmortem SKILL.md skillA
postmortem from sethgammon/citadel is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sethgammon/citadel/postmortem@git:20260611.0f3f8e7Pins git:20260611.0f3f8e7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sethgammon/citadel
- Path
skills/postmortem/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260611.0f3f8e7, committed Jun 11, 2026
- First version recorded
- Mar 29, 2026
- Size
- 6,852 bytes
- Repository stars
- 927
- License
- MIT
Auto-generates a structured postmortem from a completed campaign. Reads the campaign file, telemetry logs, and feature ledger. Produces a documented analysis of what broke, what the safety systems caught, and what patterns emerged. Can also be invoked manually for any incident.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /postmortem — Campaign Postmortem Generator
## Orientation
**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.
**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`).
## 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 /do routes "postmortem", "retro", "what broke", "what happened"
## Inputs
One of:
1. A campaign file path (.planning/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?)
…Read the whole file at its exact version.
How to install
mdr add sethgammon/citadel/postmortem@sha256:94add22a2465a768The line at the top of this page pins the label git:20260611.0f3f8e7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_r3uxrpvtq3ca5ndi)
7 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Mar 29, 2026 and Jun 11, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260611.0f3f8e7 latest | 2026-06-11 | 0f3f8e7 | 6,852 B | A | view · diff |
| git:20260611.a647953 | 2026-06-11 | a647953 | 6,839 B | A | view · diff |
| git:20260503.631b94d | 2026-05-03 | 631b94d | 6,751 B | A | view · diff |
| git:20260329.6c378a2 | 2026-03-29 | 6c378a2 | 6,681 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6852 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sethgammon/citadel · 927 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r3uxrpvtq3ca5ndi GET https://markdownregistry.com/api/v1/resolve?ref=sethgammon/citadel/postmortem GET https://markdownregistry.com/api/v1/blob/94add22a2465a768972681b90b2354f72b86752891f1d22680979a381008f666
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from sethgammon/citadel
Every file in sethgammon/citadel