postmortem

Generate structured postmortem markdown from Citadel campaign files, telemetry, and git history.

820|78|Updated Mar 20, 2026

Search Tags:#telemetry #postmortem #root-cause #audit-trail #lessons-learned #campaign-analysis

Ready to run

npx skills add https://github.com/SethGammon/Citadel --skill postmortem-sethgammon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/SethGammon/Citadel/tree/main/skills/postmortem
Command: npx skills add https://github.com/SethGammon/Citadel --skill postmortem-sethgammon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After campaigns, teams struggle to recall decisions, outcomes, and failures. This Skill automatically generates a structured postmortem from campaign data, telemetry, and git history to provide an objective retrospective.

Core Features & Use Cases

Automated postmortem generation: Aggregates campaign files, telemetry logs, and feature ledger to produce a documented analysis.
What broke analysis: Identifies failures, safety-catch activations, and patterns across the campaign lifecycle.
On-demand and post-campaign use: Run after a campaign completes or on manual request to capture lessons learned.

Quick Start

Run the /postmortem command after a campaign finishes to generate the retrospective report.

Frequently Asked Questions about postmortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a structured postmortem after a campaign completes?▼

A postmortem aggregates campaign files, telemetry data, and git history to produce a standardized markdown report. It captures what broke, safety system activations, and recurring patterns to provide an objective retrospective after campaigns complete.

What is included in a campaign postmortem report?▼

A postmortem report includes standardized sections for summary, failures, safety catches, and scope analysis. It aggregates campaign files, telemetry logs, and the feature ledger to document what broke and which safety systems caught issues.

When should I run a postmortem analysis on my campaign data?▼

Run postmortem analysis after campaigns complete, following debugging sessions, or on-demand to capture lessons learned. It reads telemetry data and the feature ledger to identify failures and safety-catch activations across the campaign lifecycle.

Can I use telemetry logs and git history for root-cause analysis?▼

Telemetry logs and git history are aggregated for root-cause analysis to identify failures and recurring patterns. The postmortem process reads campaign files and telemetry data to document what broke and which safety systems caught issues.

Where are generated postmortem reports saved?▼

Generated postmortem reports are saved as standardized markdown files to the .planning/postmortems directory. The output includes structured sections for summary, failures, safety catches, and scope analysis from the aggregated campaign data.

What's the best way to document lessons learned from a debugging session?▼

Document lessons learned by running a postmortem that aggregates telemetry and git history into a structured markdown report. It identifies what broke, which safety systems caught issues, and recurring patterns for an objective retrospective.