Overnight incident digest
A morning digest of what broke overnight, taken from the channels and tickets themselves, with the open questions listed.
The prompt
Read the incident channels and tickets I name, covering the period since this task last ran. Change nothing. Channels: LIST. Tracker: WHICH ONE, and which project or label. For each incident, one block. Title, and the identifier if there is one. Timeline. First report, first acknowledgement, the state changes, and the most recent message, each with its time and who wrote it. Current state, quoted from the most recent message rather than inferred. If nobody has written anything for hours, say how long the silence has run. Who is on it, as stated. If nobody is named, write NOBODY NAMED. Customer impact, only if someone stated it. Never estimate it. Open questions. What the thread asks and nobody has answered. Then two lists. Still open. Incidents with no stated resolution. Went quiet. Incidents with no message for over four hours and no stated resolution. This list is the point of the digest. Rules. Do not diagnose a cause. Do not judge severity. Where the thread disagrees with the ticket, show both and say they disagree.
How to use it
This one is built to be scheduled. Scheduled tasks are time-based: they do not fire from an incoming email or a changed file.
Use when incidents are discussed across a chat tool and a tracker and you want one read before the stand-up.
Vibe prepares and drafts. You verify and decide. Ask for a citation on every finding: a confident answer is not evidence.
What you get back
One block per incident with timeline, current state as stated, who is on it, and what is still unanswered.
What it writes
Nothing. This one only answers.
More for scheduled
From the source file in awesome-mistral-vibe-prompts, CC BY-SA 4.0. Not affiliated with, or endorsed by, Mistral AI.