Incident Digest
Rebuilds what happened and when, from the traffic, so the review starts from a timeline instead of
from memory.
Inputs
- Email and Teams traffic for the incident window
- Enterprise Search for any status page, runbook or change record referenced in the traffic
references/config.md for the severity vocabulary and the channels that matter
Procedure
- Establish the window. First signal to last all-clear, from the traffic itself. If the
incident is open, say so and mark the timeline as in progress.
- Build the timeline in UTC and in the user's local time, one row per event that changed what
people knew or did. Chatter that changed nothing is not an event.
- For each row: timestamp, what happened, who said it, and the source link.
- Separate three things explicitly, because post-incident reviews fail when they blur:
what was observed, what was believed at the time, and what is now known. A belief
that turned out wrong stays in the timeline, labelled, because it explains the decisions.
- List open questions with an owner each, and anything the traffic references but does not
resolve.
- Write the digest to the output folder.
Output
Timeline table, then: observed versus believed versus known, open questions with owners, and
references the traffic made to documents that were not found.
Definition of done
Every timeline row is sourced, beliefs are separated from facts, and open questions carry owners.
No blame, ever. The digest names who said what, because that is the record, and never why
anyone did or did not do something. Attributing motive is out of scope and corrosive.
When there is no data
- Sparse traffic: say the timeline is thin and name the window searched. A three-row timeline
honestly labelled is better than a padded one.
- Conflicting timestamps across systems: show both and say they conflict.
- Incident still open: mark in progress and say the all-clear was not found.
Boundaries
- Never post to a channel, never reply to a thread, never update a status page.
- Never assign an action. List open questions with suggested owners for a human to assign.
- Never state a root cause. Surface what the traffic says and label it belief or finding.
- Never include customer identifiers in the digest unless the user asks and approves.
- Draft only. The digest is written for the user. Circulating it to a review group is the
user's action, behind the normal approval prompt.
Self-check
- Is every row sourced and timestamped?
- Are beliefs at the time clearly separated from what is now known?
- Did I avoid stating a root cause or attributing motive?
1---2name: incident-digest3description: Turns the mail and Teams traffic around an incident into a dated timeline with the open questions and who owns each. Use when the user asks for an incident timeline, what happened during an outage, to prepare a post-incident review, or to catch up on an incident in progress.4metadata:5 source: https://skillmd.com/skills/kesslernity/incident-digest6---78# Incident Digest910Rebuilds what happened and when, from the traffic, so the review starts from a timeline instead of11from memory.1213## Inputs14- **Email** and Teams traffic for the incident window15- **Enterprise Search** for any status page, runbook or change record referenced in the traffic16- `references/config.md` for the severity vocabulary and the channels that matter1718## Procedure191. **Establish the window.** First signal to last all-clear, from the traffic itself. If the20 incident is open, say so and mark the timeline as in progress.212. **Build the timeline** in UTC and in the user's local time, one row per event that changed what22 people knew or did. Chatter that changed nothing is not an event.233. **For each row**: timestamp, what happened, who said it, and the source link.244. **Separate three things explicitly**, because post-incident reviews fail when they blur:25 **what was observed**, **what was believed at the time**, and **what is now known**. A belief26 that turned out wrong stays in the timeline, labelled, because it explains the decisions.275. **List open questions** with an owner each, and anything the traffic references but does not28 resolve.296. **Write** the digest to the output folder.3031## Output32Timeline table, then: observed versus believed versus known, open questions with owners, and33references the traffic made to documents that were not found.3435## Definition of done36Every timeline row is sourced, beliefs are separated from facts, and open questions carry owners.3738**No blame, ever.** The digest names who said what, because that is the record, and never why39anyone did or did not do something. Attributing motive is out of scope and corrosive.4041## When there is no data42- Sparse traffic: say the timeline is thin and name the window searched. A three-row timeline43 honestly labelled is better than a padded one.44- Conflicting timestamps across systems: show both and say they conflict.45- Incident still open: mark in progress and say the all-clear was not found.4647## Boundaries48- **Never post to a channel, never reply to a thread, never update a status page.**49- Never assign an action. List open questions with suggested owners for a human to assign.50- Never state a root cause. Surface what the traffic says and label it belief or finding.51- Never include customer identifiers in the digest unless the user asks and approves.52- **Draft only.** The digest is written for the user. Circulating it to a review group is the53 user's action, behind the normal approval prompt.5455## Self-check56- Is every row sourced and timestamped?57- Are beliefs at the time clearly separated from what is now known?58- Did I avoid stating a root cause or attributing motive?