All products

Prepare a Rootly incident review with AI

Build a review packet from incident records and authorised evidence, leaving disputed explanations and proposed improvements visible for the people in the meeting.

Prepare a Rootly incident review with AI when the service is back but the team has several different accounts of what happened. The retrospective skill helps an agent assemble a timeline and a set of questions from the records it is allowed to read. The review can proceed even when the cause is still unknown.

A code change, its deployment and the first customer report may have distinct timestamps. Placing them on the same timeline is a starting point for discussion. It does not assign fault to the author or show that the change caused the incident. Participants can add their own learning and decide which proposed actions deserve a place on the roadmap.

What it does

  • Put incident, deployment and recovery events in order with their sources.
  • Record the customer impact that can be supported by the available material.
  • Preserve conflicting accounts and turn the disagreement into a review question.
  • Flag a missing evidence source instead of treating an empty result as proof.
  • Propose an improvement with an observable test for whether it helped.

Install and use

  1. Supply an authorised Rootly incident and any approved supporting evidence. Repository or deployment history needs its own access.
  2. Ask, “Prepare the timeline for tomorrow’s review and flag which explanations about the onset still need a human to confirm them.”
  3. Bring the open questions into the meeting and let the team decide on ownership and proposed actions afterwards.

FAQ

Source

Made by Rootly. Original skill: retrospective, published on GitHub under the Apache-2.0 licence.

View on GitHub