Draft a blameless incident review with an evidence-based timeline, causes, and owned follow-ups.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this after an outage, data issue, or failed release.
Collect alerts, logs, deploys, chat messages, and status updates with timestamps. Build a timeline in one time zone: when it started, when it was noticed, key decisions, when it was fixed, and when it was confirmed fixed. Cite the source for each entry and mark gaps. Add the impact: who was affected, for how long, and what data or money was involved.
Separate the trigger from the conditions that let it cause harm: missing tests, alerts, limits, docs, or rollback. For each, give the evidence and how sure you are. If the cause is not proven, say so and list what would prove it. Describe what systems and steps did, not what people failed to do.
For each follow-up give the action, the problem it prevents, the owner, and a due date. Prefer fixes to systems over reminders to people. Keep the list short enough to finish.
Never name a person as the cause, invent a timeline entry, or claim a root cause without evidence. Do not publish the review or close follow-ups; the incident owner approves it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.