skills.rest
Doumajnik
DoumajnikCOMMUNITY
Explore all skills by this author →
GitHub

incident-response

Coordinate end-to-end response for production incidents from detection to postmortem.

3|Updated Feb 24, 2026
Search Tags:#devops#root cause analysis#incident response#postmortem#incident management#production outage#sev1
One-click install
npx skills add https://github.com/Doumajnik/template --skill incident-response-doumajnik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/Doumajnik/template/tree/main/.github/skills/incident-response
Command: npx skills add https://github.com/Doumajnik/template --skill incident-response-doumajnik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unplanned production outages, degradations, and security breaches leave engineering teams scrambling without a standardized process to coordinate response, minimize downtime, identify root causes, and prevent future incidents.

Core Features & Use Cases

  • 7-Phase Standardized Pipeline: Follows a consistent workflow from incident declaration through stabilization, parallel investigation, root cause confirmation, permanent fix deployment, resolution validation, and blameless postmortem.
  • Severity-Tailored Workflows: Custom update cadences and observation windows for SEV1, SEV2, and SEV3 incidents aligned to business impact.
  • Real-World Use Case: For an e-commerce site experiencing checkout failures during a sales event, this skill guides the team to stabilize the system, investigate the root cause (e.g., a misconfigured database connection pool), deploy a permanent fix, and run a postmortem to avoid recurrence.

Quick Start

Use the incident-response skill to handle the current production outage where customer checkout is returning 500 errors.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I manage a production outage and coordinate incident response across teams?▼

Production incident management uses a structured end-to-end workflow that coordinates parallel investigators, validates root causes with evidence, and deploys permanent fixes to resolve unplanned outages.

What is the best way to run a blameless postmortem after resolving a SEV1 incident?▼

Blameless postmortem generation is the final phase of the standardized incident response pipeline, documenting root cause analysis and resolution steps to prevent future production outages.

Can I use this incident management workflow for security breaches and error rate surges?▼

Yes, incident management workflows apply to live customer-facing failures, suspected system attacks, and security breaches, coordinating cross-team action to stabilize and resolve critical production incidents.

How do I classify severity and tailor workflows for SEV1, SEV2, and SEV3 incidents?▼

Severity classification tailors incident response workflows by applying custom update cadences and observation windows for SEV1, SEV2, and SEV3 incidents aligned to business impact.

How to validate a root cause analysis before deploying a permanent fix during a production outage?▼

Root cause validation during a production outage requires evidence-based confirmation within the parallel investigation phase before proceeding to permanent fix deployment and resolution validation.

Related Skills

Explore More Software Engineering Skills→
LucasMalessaLucasMalessa

ops-incident-response

Coordinate production incident phases from detection to post-incident review.

Community
Advanced
qa-amanqa-aman
19

postmortem

Document blameless postmortems with timelines, 5 Whys, and action items.

Community
Advanced
tarunccettarunccet
5

ai-incident-response

Classify and respond to AI model failures with severity runbooks.

Community
Advanced
w95w95
145

incident-response

Manage production incidents from detection through blameless postmortem documentation.

Community
Intermediate