Skip to main content
Traversal can generate a post-mortem from any incident — by scanning the Slack channel where your team worked through it, or from context you provide directly in the web app.

​
In Slack — on demand

Once an incident is resolved, tag @Traversal in the channel and ask for a post-mortem:
@Traversal can you write a post-mortem for this incident?
Traversal scans the channel — pulling in the timeline, key decisions, relevant alerts, and investigation findings — and posts a structured post-mortem directly in the channel.
You can guide the output by adding context in your message: @Traversal write a post-mortem focusing on the database layer — the root cause was a connection pool exhaustion.

​
In Slack — automatically

Traversal runs a persistent agent in your incident channels. When it detects that an incident has been resolved, it will automatically generate and post a post-mortem without any manual trigger.
Automatic post-mortems require Traversal to be running in your incident channel. Reach out to your Traversal contact to enable this.

​
In the web app

You can generate a post-mortem from the Traversal web app by providing context on the incident — either 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 pulls from the thread, its own investigation findings, and any other context you provide to produce a complete post-mortem.