incident-response-playbook
Skill0 starsChanged 4 months agoMITView on GitHub
Enforce a calm, evidence-based incident response workflow. Use for production incidents, outages, reliability events, and post-incident follow-up.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- blamejs/exceptd-skillstheir own version, first seen Aug 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- blamejs/exceptd-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- architect-modeSkill
- architecture-bundleSkill
- code-like-a-localSkill
- decision-making-guardrailsSkill
- decision-recordsSkill
- delivery-bundleSkill
- fable-modeSkill
- finish-the-turnSkill
- launch-readiness-gateSkill
- lead-developer-modeSkill
- lead-with-outcomeSkill
- lean-tool-useSkill
- migration-refactor-safetySkill
- plan-before-implementationSkill
- pr-and-commit-hygieneSkill
- product-delivery-bundleSkill
- product-minded-engineer-modeSkill
- reliability-bundleSkill
- reliability-incident-modeSkill
- review-quality-gateSkill
- run-guardrails-on-code-changesSkill
- security-bundleSkill
- security-minded-engineer-modeSkill
- senior-operating-systemSkill
- staff-engineering-bundleSkill
- staff-engineer-modeSkill
- stakeholder-communicationSkill
- surgical-questionsSkill
- systematic-debuggingSkill
- test-disciplineSkill
- truthful-reportingSkill
- verify-by-exercisingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Do not close or summarize an incident until the system is stable, the cause is understood, and the follow-up is clear.
- Distinctive: line 18
Verify the mitigation before declaring progress.
- Distinctive: line 24
Prefer reversible mitigations over speculative changes.
- Distinctive: line 25
Document what changed, what was observed, and what remains uncertain.
- Distinctive: line 30
Do not declare the incident resolved without verification.
- Distinctive: line 31
Do not treat a mitigation as a root cause explanation.
- Distinctive: line 32
Do not leave the team without clear next actions.
- Distinctive: line 33
Do not end the incident without learning and hardening steps.
- Distinctive: line 35
Use this skill to make incident handling disciplined, transparent, and durable.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Incident response playbook
Do not close or summarize an incident until the system is stable, the cause is understood, and the follow-up is clear.
This skill is the completion gate for incident work — the checks that must pass before an incident can be called handled. For the fuller investigative and operating posture during an incident, see reliability-incident-mode; the two are designed to be used together.
Response flow
- Stabilize the situation first.
- Preserve evidence and current symptoms.
- Separate facts from assumptions.
- Identify the likely cause and the blast radius.
- Verify the mitigation before declaring progress.
- Turn the incident into concrete follow-up actions.
Required incident practices
- Contain the blast radius when possible.
- Prefer reversible mitigations over speculative changes.
- Document what changed, what was observed, and what remains uncertain.
- Make the post-incident follow-up explicit and owned.
Non-negotiables
- Do not declare the incident resolved without verification.
- Do not treat a mitigation as a root cause explanation.
- Do not leave the team without clear next actions.
- Do not end the incident without learning and hardening steps.
Use this skill to make incident handling disciplined, transparent, and durable.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.