incident-response

Coordinate structured incident response for production outages with mitigation ranking and recovery handoff.

108|27|Updated Mar 26, 2026

Search Tags:#workflow #postmortem #escalation #mitigation #incident #incident-response #outage

Ready to run

npx skills add https://github.com/diegosouzapw/omni-skills --skill incident-response-diegosouzapw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/diegosouzapw/omni-skills/tree/main/skills/incident-response
Command: npx skills add https://github.com/diegosouzapw/omni-skills --skill incident-response-diegosouzapw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Structured incident response reduces time-to-stabilization by providing a repeatable workflow for outage triage, mitigation sequencing, stakeholder communication, and post-incident handoff.

Core Features & Use Cases

Framing the incident with clear scope, severity, ownership, and initial timeline.
Ranking and selecting reversible mitigations, coordinating cross-team actions, and setting a cadence for updates.
Producing a clean recovery packet, documenting decisions, and outlining follow-up actions for postmortem.

Quick Start

Frame the incident scope, assign ownership, and generate a recovery timeline for a fast, structured response.

Frequently Asked Questions about incident-response

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate incident response for a production outage?▼

Incident response coordination requires a defined incident frame, clear roles, and mitigation options to reduce time-to-stabilization during a production outage. You structure triage, rank reversible mitigations, and set a communications cadence across teams.

What is the best way to structure outage mitigation across multiple teams?▼

Outage mitigation across multi-team incidents requires ranking reversible actions, coordinating cross-team execution, and setting a strict update cadence. This structured approach ensures stakeholders receive timely communications while teams execute recovery actions.

How does an incident response workflow handle postmortem handoff?▼

Incident response workflow handles postmortem handoff by producing a clean recovery packet that documents decisions, timelines, and follow-up actions. This output pack ensures the post-incident review has all necessary context for analysis.

What do I need to start structured incident response during severe service degradation?▼

To start structured incident response during severe degradation, you need a defined incident frame, assigned ownership, roles, mitigation options, and escalation paths. Frame the incident scope and generate a recovery timeline to begin.

When should I use a structured incident response workflow?▼

You should use a structured incident response workflow during production outages or severe service degradations. It applies when you need coordinated framing, mitigation ranking, communication cadence, and recovery handoff to reduce time-to-stabilization.

Can I rank and select reversible mitigations during an active outage?▼

Yes, you can rank and select reversible mitigations during an active outage. The workflow enables evaluating mitigation options, coordinating cross-team actions, and setting a communications cadence to ensure structured recovery.