incident-response

Coordinate structured incident response workflows for production outages.

3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/vndee/engineering-skills --skill incident-response-vndee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/vndee/engineering-skills/tree/main/.claude/skills/incident-response
Command: npx skills add https://github.com/vndee/engineering-skills --skill incident-response-vndee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production incidents disrupt users and degrade trust; without a clear playbook, responses are slow, inconsistent, and error-prone. This skill provides a structured incident management approach that prioritizes service restoration, faster recovery, and thorough postmortem learning.

Core Features & Use Cases

  • Robust six-step workflow: Detect & Acknowledge, Triage, Mitigate, Investigate Root Cause, Fix & Verify, Postmortem, designed to guide engineers through every phase of an outage.
  • Runbook templates and evidence gathering: templates for timelines, root-cause analysis, and postmortems to ensure repeatable, documented responses.
  • Scalable to teams of any size: applies to single-service outages or multi-service incidents, with clear handoffs and escalation paths.

Quick Start

Start the incident response workflow by detecting the incident, triaging with the provided tools, mitigating to restore service, and performing root-cause analysis followed by a postmortem.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I structure incident response to restore production services during an outage?

Incident response is structured through a six-step workflow: Detect & Acknowledge, Triage, Mitigate, Investigate Root Cause, Fix & Verify, and Postmortem. This guides engineers through every outage phase to prioritize service restoration and faster recovery.

What is the best way to document root-cause analysis and postmortems after an outage?

Root-cause analysis and postmortems are documented using provided runbook templates for timelines and evidence gathering. This ensures repeatable, formally documented responses that capture thorough postmortem learning across teams.

Can I use a single incident workflow for multi-service production outages?

Yes, this incident workflow scales to teams of any size and applies to both single-service and multi-service outages. It coordinates structured response with clear handoffs and escalation paths across systems.

How does incident triage work when detecting a production incident?

Incident triage works by applying structured detection and acknowledgment steps to assess the production incident. It coordinates triage using provided tools to guide mitigation efforts and restore service quickly.

Do I need external dependencies to run incident response and postmortem workflows?

No external dependencies are required to run incident response and postmortem workflows. The skill operates independently to coordinate detection, triage, mitigation, root-cause analysis, fixes, and postmortem documentation.

Why should I use a formal incident response playbook instead of ad-hoc mitigation?

A formal incident response playbook prevents slow, inconsistent, and error-prone mitigation during production outages. It provides a structured incident management approach that prioritizes service restoration and thorough postmortem learning to rebuild user trust.