incident
Skill11 starsChanged 11 days agoMITView on GitHub
Production incident management — triage, mitigate, root-cause analysis, and post-incident review. Use when the user says "the site is down", "error rates are spiking", "we have a production incident", "do a postmortem", or invokes /incident.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- Yesterday-AI/ytstacktheir own version, first seen Nov 16, 2026
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
- AsiaOstrich/EngramGraphtheir own version, first seen Nov 8, 2026
- AsiaOstrich/universal-dev-standardstheir own version, first seen Nov 1, 2026
- fervaldezjr/agent-opstheir own version, first seen Nov 1, 2026
- umararshad4/honey-stacktheir own version, first seen Nov 1, 2026
Used with
Projects with it also use db-review, runbook and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
tranhieuttSkilldb-review
Also in 3 projects that use this
AnthropicSkillrunbook
Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.
Also in 4 projects that use this
MicrosoftSkillperf
Speed and memory performance rules for Rust crates, the Node addon, webui-framework, and webui-delivery.
Also in 4 projects that use this
drewdrewthisSkillsweep
Search for similar patterns, anti-patterns, or issues elsewhere in the codebase after a fix or feature. Use after implementing a fix to catch the same bug in other places, or proactively to audit for a known pattern.
Also in 3 projects that use this
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 5 projects that use this
mijunriSkilldatabase
数据库脚本与操作规范。脚本放在 db_scripts 目录,遵循查询优化、事务、安全等实践。
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- alexj11324/Mikka★ 87same name
- AsiaOstrich/universal-dev-standards★ 84same name
- DataWithBaraa/claude-code-data-engineering-skills★ 84same name
- manusco/resonance★ 38same name
- ulises-jeremias/agent-toolkit★ 20same name
- NotHarshhaa/devops-skills★ 8same name
- greglas75/zuvo★ 7same name
- umararshad4/honey-stack★ 5same name
- AsiaOstrich/EngramGraph★ 4same name
- gonimar/claude-web-studio★ 4same name
13 more not listed
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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-dataSkill
- brainstormingSkill
- craft-lessonSkill
- create-agentSkill
- create-skillSkill
- customize-agentSkill
- customize-skillSkill
- designSkill
- deslopSkill
- developSkill
- discovery-reportSkill
- elicitationSkill
- empathy-mapSkill
- explore-ideaSkill
- grill-meSkill
- help-meSkill
- humanizeSkill
- iterateSkill
- journey-mapSkill
- jtbdSkill
- kanbanSkill
- launchSkill
- legal-safety-auditSkill
- maintenance-executeSkill
- maintenance-planSkill
- memorySkill
- motionSkill
- phaseSkill
- planSkill
- research-planSkill
- retroSkill
- reviewSkill
- root-causeSkill
- round-tableSkill
- shape-upSkill
- shut-upSkill
- statusSkill
- teach-meSkill
- testSkill
- unpack-problemSkill
- validate-ideaSkill
- validation-patternsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
When something breaks in production, this skill provides the structured process to triage, mitigate, analyze, and prevent recurrence.
- Distinctive: line 42
Stop the bleeding: rollback, feature flag off, scale up, redirect traffic
- Distinctive: line 45
Document what was done and timeline
- Distinctive: line 69
Add regression tests that would have caught this
- Distinctive: line 81
Update runbooks with the new failure mode
- Distinctive: line 152
Close the loop: Every incident must produce at least one prevention action item.
- Distinctive: line 153
No silent fixes: Every remediation goes through review and QA, even in an incident.
- Very specific: line 165
After incident is resolved → load iterate to address follow-up improvements
- Very specific: line 166
If incident reveals architectural issues → load develop for broader redesign
- Very specific: line 167
If incident response process needs review → load retro
- Distinctive: line 178
Run this for every incident directory, before it is treated as closed:
- Distinctive: line 212
If pipeline is uninitialized (e.g., the project has no pipeline state yet but has a live incident), initialize with the current project …
- Distinctive: line 228
File a Change Request for cross-team fixes: If remediation requires a change in another team's domain (e.g., a UX change requested by the …
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Incident — Production Response Workflow
What this skill does
When something breaks in production, this skill provides the structured process to triage, mitigate, analyze, and prevent recurrence. It is not for feature development — it is for when the system is down, errors are spiking, or users are reporting critical problems.
This skill is reactive. It is invoked when a production issue is detected, not during normal development.
Workflow steps
Step 1: Triage
Invoke @product-manager to lead triage:
- Severity classification:
- SEV1 (Critical): Service down, data loss, security breach → all hands, immediate response
- SEV2 (High): Major feature broken, significant user impact → urgent response, 4-hour target
- SEV3 (Medium): Feature degraded, workaround exists → next business day
- SEV4 (Low): Minor issue, cosmetic, low impact → backlog
- Assign incident commander (default: @product-manager)
- Assemble responders based on issue type:
- Infrastructure issue → @devops-engineer + @architect
- Application bug → @developer + @tech-lead
- Security incident → @security-engineer + @devops-engineer
- Performance degradation → @performance-engineer + @architect
- Open incident channel — create
artifacts/output/08-incidents/INC-NNN/directory
Output: artifacts/output/08-incidents/INC-NNN/triage.md (Use template: .agents/templates/incident/incident-triage-template.md)
Step 2: Mitigate
The first priority is user impact reduction, not root cause.
Invoke appropriate responders to:
- Stop the bleeding: rollback, feature flag off, scale up, redirect traffic
- Communicate status to stakeholders (internal and external if applicable)
- Preserve evidence: logs, traces, screenshots, user reports
- Document what was done and timeline
Key rule: Mitigate first, analyze second. Never debug in production when a rollback fixes the user-facing issue.
Output: artifacts/output/08-incidents/INC-NNN/mitigation.md
Step 3: Root-Cause Analysis
Once users are unblocked, invoke @architect or @tech-lead to lead RCA:
- 5 Whys analysis — drill to root cause
- Timeline reconstruction — from first signal to mitigation
- Contributing factors — what conditions allowed this to happen
- Detection gaps — why wasn't this caught before reaching users
- Prevention mechanisms — what would stop this class of issue in the future
Output: artifacts/output/08-incidents/INC-NNN/rca.md (Use template: .agents/templates/incident/rca-template.md)
Step 4: Remediation (parallelizable)
Invoke appropriate agents for the fix. Code fix and monitoring improvements can run in parallel.
Step 4a: Code Fix ⟨parallel⟩
Invoke @developer (or @devops-engineer for infra issues) to:
- Fix the root cause
- Add regression tests that would have caught this
Then (sequential within this path):
@code-reviewerreviews the fix@qa-engineervalidates the fix and regression tests@devops-engineerdeploys the fix
Loop limit: Max 2 review cycles on the incident fix. If the fix is still contested, the incident commander (@product-manager) makes the ship/rollback call.
Step 4b: Monitoring Improvements ⟨parallel⟩
Invoke @devops-engineer to:
- Improve monitoring/alerting to detect similar issues earlier
- Update runbooks with the new failure mode
Output: artifacts/output/08-incidents/INC-NNN/remediation.md
Step 5: Post-Incident Review
Invoke @product-manager to conduct a blameless post-incident review:
- What happened — timeline of events
- What was the impact — users affected, duration, data impact
- What was the root cause — from RCA
- What was the mitigation — what stopped the bleeding
- What was the remediation — what prevents recurrence
- What went well — things that worked (monitoring, response time, etc.)
- What could be improved — detection, response, communication, prevention
- Action items with owners and deadlines
Output: artifacts/output/08-incidents/INC-NNN/post-incident-review.md (Use template: .agents/templates/incident/post-incident-review-template.md)
Step 6: Update Knowledge Base
Invoke @product-manager to write incident learnings to memory via @memory-controller:
@memory-controller write blockers-and-risks.md
### [RISK] {incident title} [date: YYYY-MM-DD] [agent: @product-manager] [RESOLVED: YYYY-MM-DD]
{new risks identified from this incident}
**Status:** resolved
@memory-controller write lessons-learned.md
### [LESSON] {title} [date: YYYY-MM-DD] [agent: @product-manager]
{incident lessons — what happened, root cause, prevention}
**Status:** active
@memory-controller write patterns-and-conventions.md
### [PROCESS] {title} [date: YYYY-MM-DD] [agent: @product-manager]
{new guardrail or operational pattern established}
**Status:** activeWrite session summary:
@memory-controller session-write
Worked on: Incident response — INC-NNN ({brief description})
Decisions made:
- Severity: {SEV level}
- Mitigation: {what was done to stop user impact}
- Root cause: {one sentence}
- Prevention: {key action item}
Next step: {follow-up improvements via iterate, or "monitoring for recurrence"}
New blockers: {any new risks identified, or "none"}Output artifacts
artifacts/output/08-incidents/INC-NNN/triage.mdartifacts/output/08-incidents/INC-NNN/mitigation.mdartifacts/output/08-incidents/INC-NNN/rca.mdartifacts/output/08-incidents/INC-NNN/remediation.mdartifacts/output/08-incidents/INC-NNN/post-incident-review.md
When to use
Use this when:
- A production service is down or critically degraded
- Error rates spike unexpectedly
- Security vulnerability is discovered in production
- Data integrity issue is detected
- Performance degrades below SLA thresholds
Key principles
- Mitigate first, analyze second. Reduce user impact before finding root cause.
- Blameless. Focus on systems and processes, not people.
- Document everything. Future incident responders need the timeline.
- Close the loop. Every incident must produce at least one prevention action item.
- No silent fixes. Every remediation goes through review and QA, even in an incident.
Severity-specific SLAs
| Severity | Response Time | Mitigation Target | Update Cadence |
| SEV1 | 15 minutes | 1 hour | Every 30 minutes |
| SEV2 | 30 minutes | 4 hours | Every hour |
| SEV3 | 4 hours | Next business day | Daily |
| SEV4 | Next business day | Next sprint | Weekly |
Handoff
- After incident is resolved → load
iterateto address follow-up improvements - If incident reveals architectural issues → load
developfor broader redesign - If incident response process needs review → load
retro
Done when — checked mechanically
/incident shipped for its whole life with no gate: an incident directory could hold a triage record
and nothing else, and nothing noticed. The skill's own principle — "close the loop, every incident
must produce at least one prevention action item" — was a sentence nobody could falsify, and the
SEV1 SLA promised a 15-minute response with nothing that reads a clock.
Run this for every incident directory, before it is treated as closed:
node .agents/scripts/incident_record_check.js check \
--dir artifacts/output/08-incidents/INC-NNN --jsonIt requires a recorded SEV1-SEV4 severity, all five named artifacts present and substantial (a stub satisfies "the file exists" while recording nothing), a post-incident review — mandatory at SEV1 and SEV2 — at least one prevention action item carrying both an owner and a date, and blameless phrasing.
What it does not check: whether mitigation met the SLA, whether the RCA is correct, or whether the severity was honestly classified. Those need someone who was there. A green result means the record is complete and the loop was closed — not that the response was good.
Exit 0 conformant · 1 failures · 2 usage/IO error, fail-closed.
State Machine Integration
The pipeline state machine (node .agents/scripts/orchestrator_state.js) is the canonical record of project state. This skill must wire its work into it so other skills, the dashboard, and the code-graph see what happened.
At Start
Run:
node .agents/scripts/orchestrator_state.js statusLoad incident context before triage:
@memory-controller load product-manager [incident — {brief description of symptoms}]If pipeline is uninitialized (e.g., the project has no pipeline state yet but has a live incident), initialize with the current project name and type before recording. If the pipeline is mid-workflow, do NOT advance the phase — incident work happens in parallel.
At End — Record Completion
For each incident directory artifacts/output/08-incidents/INC-NNN/, record the artifacts produced:
node .agents/scripts/orchestrator_state.js complete --agent devops-engineer --artifact 08-incidents/INC-NNN/triage.md
node .agents/scripts/orchestrator_state.js complete --agent devops-engineer --artifact 08-incidents/INC-NNN/mitigation.md
node .agents/scripts/orchestrator_state.js complete --agent architect --artifact 08-incidents/INC-NNN/rca.md
node .agents/scripts/orchestrator_state.js complete --agent developer --artifact 08-incidents/INC-NNN/remediation.md
node .agents/scripts/orchestrator_state.js complete --agent devops-engineer --artifact 08-incidents/INC-NNN/post-incident-review.mdReplace INC-NNN with the actual incident ID. The developer complete call will trigger a code-graph refresh, ensuring the next agent (e.g., a follow-up architect reviewing the architectural impact) sees the new code state.
File a Change Request for cross-team fixes. If remediation requires a change in another team's domain (e.g., a UX change requested by the architect but owned by the product manager), file a CR:
node .agents/scripts/orchestrator_state.js file-cr --from developer --to product-manager --target <file> --issue "<issue>"This creates an open CR in pipeline-state.json that blocks phase advancement until resolved.
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.

