> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traversal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Post-mortems

> Generate a post-mortem from a Slack incident channel or the Traversal web app, automatically or on demand.

Traversal drafts a post-mortem for a resolved incident: a timeline, a root cause analysis, and suggested follow-ups. You review and edit the draft. You can generate one from Slack or the Traversal web app.

## In Slack

If your team runs incident response in Slack, you can get a post-mortem there in two ways:

* Proactively: Traversal generates and posts a post-mortem once the room reaches consensus that the incident is resolved.
* Manually: you ask for one by tagging Traversal in the channel.

### Proactive

When an [Incident Worker](https://docs.traversal.com/using-traversal/incident-workers.md) is active in an incident channel, it follows the incident in real time and, once the room reaches consensus that the incident is resolved, automatically generates and posts a post-mortem in the channel. No `@Traversal` mention required.

#### How Traversal assembles it

Because Traversal investigated the incident in real time, it has two sources to draw from when the incident closes:

1. Its initial investigation: the timeline, evidence, and hypothesized root cause Traversal produced at the start of the incident.
2. The channel conversation: what the team said, shared, and concluded, including decisions, handoffs, fixes applied, and the final resolution.

Traversal reconciles the two into a single narrative. It calls out where its initial analysis was correct, where it diverged from what the team found, and where it lacked the visibility to make a call.

#### What to expect

Proactive post-mortems include:

| Section | Contents |
| :- | :- |
| Summary | Severity, duration, date, and a paragraph on customer and system impact |
| Timeline | A chronological sequence of alerts firing, log patterns emerging, user actions, and remediation steps, built from both the investigation and the channel |
| 5 Whys root cause analysis | A layered walk from symptom to underlying cause |
| Traversal's initial analysis | A comparison of Traversal's initial analysis with the final root cause, flagging where it was correct, where it was off, and where it couldn't see enough to be sure |
| Suggested alerts and tests | Alert conditions, log queries, or test ideas you can copy that would have caught this incident earlier, with rationale tied to the data seen during the incident |

### Manual

You can also request a post-mortem directly. Once an incident is resolved, tag `@Traversal` in the channel and ask:

> `@Traversal can you write a post-mortem for this incident?`

Traversal scans the channel for the timeline, key decisions, relevant alerts, and investigation findings, then posts a structured post-mortem in the channel.

> [!TIP]
>
> Traversal reads the full channel either way, so a plain `@Traversal write a post-mortem` is enough. If you want to steer the output, add context, for example `@Traversal write a post-mortem focusing on the database layer; the root cause was connection pool exhaustion`.

To change the format of the post-mortems a Worker writes, add [Worker instructions](https://docs.traversal.com/using-traversal/customization.md#worker-custom-instructions). See [Customization](https://docs.traversal.com/using-traversal/customization.md) for how they relate to other instruction layers.

## In the web app

You can generate a post-mortem from the Traversal web app by providing context on the incident: a description, a link to the Slack channel, or both:

> `Write a post-mortem for the checkout service outage on April 14 starting at 14:32 UTC. Here's the thread: [link]`

Traversal draws on the thread, its own investigation findings, and any other context you provide.

## Following up

The post-mortem is a starting point. Keep the conversation going in the same Slack thread or in the web app to refine the draft, clarify details, or start new analysis. You can ask Traversal to:

* Rewrite a section: `make the summary more concise` or `expand the timeline with anything that happened before 10:15 UTC`.
* Explain its reasoning: `why do you think the DB was the bottleneck and not the upstream service?`
* Go deeper: `run a new investigation on the database connection pool during this window` or `what else was deployed that day?`
* Draft follow-ups: `turn the suggested alerts into a list of Jira tickets` or `write up the action items for the next review meeting`.

> [!NOTE]
>
> Traversal's post-mortem is a draft, not a replacement for your post-incident review process.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.