Post-Mortem Writer

Auto-prepares post-mortem doc after incidents

// The problem

After major incident, team is tired, post-mortem writing slides to next week. Memories incomplete, learning lost, repeat incidents.

// What it does

Collects incident channel messages + monitoring data + deploy events. Generates structured doc in standard post-mortem template (timeline, impact, root cause, action items). One-click to Notion/Confluence.

// Value

Post-mortem writing time 4 hours → 30 minutes

All incidents get post-mortems, learning loop established, repeat incidents decrease.

Setup time: 3-5 gün

// How it works

  1. 01

    Incident channel (Slack) mesaj geçmişi

  2. 02

    Datadog/Sentry/CloudWatch ilgili dönem metric

  3. 03

    Deploy event timeline

  4. 04

    Mesaj zaman damgalı timeline reconstruction

  5. 05

    Impact calculation (etkilenen kullanıcı, downtime, revenue)

  6. 06

    Root cause + action items extraction

  7. 07

    Notion/Confluence post-mortem doc

// Real example

Bir SaaS DB outage sonrası, Selin SRE lead Slack channel + Datadog'u verdi. 20 dakikada hazır post-mortem: timeline (15dk granularity), impact (30dk downtime, 12K kullanıcı), root cause (connection pool exhaustion), 5 action item.

// Trigger

Manuel (incident resolve sonrası)

// Output channels

NotionPDFEmailLinear

// Integrations

SlackDatadogSentryCloudWatchPagerDutyNotionConfluenceLinear

// Limits (honest)

  • ×Slack channel + monitoring erişimi şart
  • ×AI taslak hazırlar; final analiz + action item önceliklendirme SRE lead
  • ×Çok karmaşık multi-service incident'larda manuel review

// SSS

01.Hangi post-mortem template?+

Google SRE / Atlassian template default. Kendi template'inizi de kullanabilirsiniz.

// Tech stack

OpenAISlack APIMonitoring APIs
~/order-postmortem-writer

// Don't see the one you need? Tell us — we ship in 2 days.

Request this agent

// More in this category