postmortem

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.

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.

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.

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.

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.

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.