Skip to content
TulipFarm

Incident postmortem agentThe review, drafted while it is fresh.

Point it at the incident channel. It reads the thread and the pull requests around it, builds a timeline and drafts a blameless review for the team to finish.

Sign up for CloudWatch one run

Your first signup includes $50 in free credits.

After an incident

Draft the postmortem

Reads
Incident channel, related PRs
Grows
A timeline and draft
Lands in
Confluence
SlackGitHubConfluence
Draft the postmortem: starts After an incident, uses Slack, GitHub, Confluence.

Ask for it once, in plain words.

No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.

You

When I give you an incident channel, read it and the pull requests merged that day. Write a timeline, what we know about the cause, and open questions. Keep it blameless.

TulipFarm

I made an agent called Postmortem writer and a manual workflow. It reads Slack and GitHub. Creating the Confluence page asks you first. Activate it?

ActivateEdit first

One incident, start to finish.

Every run is saved as an agent task you can open, check and rerun.

  1. Manual

    You name the incident channel

    Run startedStarted
  2. Reads

    The channel history in Slack

    84 messages
  3. Reads

    Pull requests merged near the incident in GitHub

    5 pull requests
  4. Writes

    A timeline and review, using your postmortem skill

    1 draft
  5. Asks first

    Create the page in Confluence

    Approved
  6. Creates

    Postmortem page

    Page readyCompleted

A draft the team finishes together.

Facts come from the thread. What it cannot tell, it lists as a question.

What gets planted.

Three parts you own and can change at any time.

  1. Agent

    Postmortem writer

    Reads the thread and drafts the review.

  2. Skill

    Blameless format

    Your sections and a rule to name causes, not people.

  3. Workflow

    After an incident

    Starts when you name a channel.

Uses

  • SlackSlack
  • GitHubGitHub
  • ConfluenceConfluence

Add if you use it

  • JiraJira
  • Google CalendarGoogle Calendar
  • Google DocsGoogle Docs

It reads quietly. It asks before it acts.

Reads without asking

  • The incident Slack channel
  • Pull requests merged around the time
  • Your postmortem template

Asks you first

  • Creating the Confluence page
  • Opening follow-up tickets

It uses your own connections, so it never sees more than you can.

Grow it your way.

  • Follow-up tickets

    Turn action items into Jira tickets, one by one, after you approve.

  • Call the review

    Draft a calendar invite for the review meeting.

  • Use Google Docs

    Write the draft to a Google Doc if you do not use Confluence.

Questions, answered.

Does it find the root cause?

No. It sets out the facts from the thread and the code changes. The team decides the cause.

Can it read private channels?

Only the ones your own Slack connection can open.

Will it assign blame?

Your skill tells it to name causes, not people. You still read the draft before it is saved.

TulipFarm for engineering

Learn from it while it is fresh.

Public beta, open to everyone. Your first signup includes $50 in free credits.

Sign up for CloudTake the browser tour