What happened, why the system allowed it, and what changes. No names in the blame column.
A blameless incident report with an exact timeline, contributing conditions, a fix, and follow-ups that each have an owner and a date.
After an incident, the report is often written to settle who was at fault. It ends with someone being reminded to be more careful, the same conditions stay in place, and the same failure returns a few months later with a different person involved.
Incident Report works from the raw facts: messages, timestamps, and what people knew at the time. It builds the timeline, asks why the failure was possible until it reaches a condition in the system, and separates the immediate fix from the changes that prevent a repeat. A final pass removes blame.
What it produces.
- →A three-sentence summary with impact in time, money, or customers
- →A neutral timeline with gaps marked, not filled
- →Contributing conditions traced to missing checks or unclear handoffs
- →Follow-ups with owner, due date, and a way to confirm they worked
- ✦Operations managers documenting an outage, miss, or wrong shipment
- ✦Small-business owners who want fewer repeat mistakes
- ✦Team leads writing up a near miss for the team
- →incident-report.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to
~/.claude/skills/ - →incident-report-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
- →A README inside the zip with install steps for Claude, ChatGPT, and Gemini
No subscription · free updates within v1.x
Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable
Before you buy.
How is this different from just asking Claude directly?
Asked cold, Claude often writes a tidy narrative that quietly settles on a person or a vague cause such as carelessness. This one demands exact times, keeps assumptions apart from facts, keeps asking why until it reaches a system condition, and rewrites any follow-up that amounts to a warning.
How is this different from a Tool?
Playbooks are systematically produced to a fixed template and priced accordingly ($12.99). Tools are hand-built, one at a time, and go deeper ($39 to $199). A Playbook gives you a reliable method for routine work; a Tool is for when the judgment matters more than the format.
Will this work with ChatGPT, Gemini, and other LLMs?
Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.
Can I share this with my team?
It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Playbook itself in the hands of a whole team, email hello@authority.md about team licensing.
What if it doesn't work for me?
If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.