Incident notes and timeline compiled into a postmortem draft while the details are still fresh.
Postmortems decay by the hour. By next Tuesday, the timeline is reconstructed from chat scrollback and memory, and the honest 2am details have been politely forgotten.
The document everyone agrees is the most valuable in engineering is the one nobody has time to write properly, right after the week they can least afford it.
This routine compiles the incident's notes, timeline, and chat record into a structured postmortem draft: what happened, when, why, and what follows.
You edit for nuance and blamelessness. The skeleton -- the part that takes hours -- is already standing.
Copy this prompt into a new Littlebird routine. Edit the days and times to fit your schedule.
Every Monday draft postmortems for any incidents from the past week using meeting notes and context
You can fake this with a chat skill and enough copy-paste. Most people keep it up for a week, then stop -- because the copy-paste is the actual job.
A routine removes the choreography: the context is already there, the schedule is already set, and the output shows up where you need it.
And it is private by design: SOC 2, GDPR and CCPA aligned, running on your Mac.
Right after the incident closes, while everything is fresh. Trigger it from your notes and the draft assembles.
No. It compiles facts and timeline. The culture of the document stays with the humans.
Plus: $17 a month ($20 month-to-month) after the free trial, with every routine included.
Yes. Plus at $17 a month ($20 month-to-month) covers the product, routines, and help when you need it.
Put Littlebird to work.
