incident-response

Coordinate triage, mitigation, communication, and postmortem for SEV1-SEV4 production incidents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SMOrchestra-ai/smorch-brain --skill incident-response-smorchestra-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/SMOrchestra-ai/smorch-brain/tree/main/plugins/engineering/skills/incident-response
Command: npx skills add https://github.com/SMOrchestra-ai/smorch-brain --skill incident-response-smorchestra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident response mitigates the chaos and high business impact caused by production outages and degraded services by providing a clear, repeatable process for triage, communication, mitigation, and postmortem analysis to reduce mean time to resolution (MTTR).

Core Features & Use Cases

  • Severity Classification: Clear SEV1–SEV4 criteria to quickly determine impact and required urgency.
  • Response Framework: Step-by-step guidance for triage, assigning an incident commander, communicating status, mitigating immediate impact, and implementing a verified resolution.
  • Postmortem & Continuous Improvement: Blameless postmortem format with timeline, root cause analysis (5 whys), and tracked action items with owners and due dates.
  • Use Case: For a production database outage affecting all users, use this Skill to classify as SEV1, assign roles, coordinate mitigation steps, issue customer and internal communications, and run a postmortem after resolution.

Quick Start

Report the incident with severity and scope, for example: 'We have a SEV1: production API down in us-east-1; start incident response, assign an incident commander, notify SRE and product leads, and publish a status update'.

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 involves classifying the outage severity, assigning an incident commander, executing mitigation steps, issuing status updates, and conducting a blameless postmortem to reduce mean time to resolution.

What is the difference between SEV1 and SEV4 incident severity levels?

Severity classification distinguishes SEV1 through SEV4 events based on scope and business impact. SEV1 indicates critical production outages affecting all users requiring immediate urgency, while SEV4 represents minor degraded services with limited impact.

How do I run a blameless postmortem after resolving an incident?

A blameless postmortem documents the incident timeline, performs root cause analysis using the 5 whys method, and tracks actionable items with assigned owners and due dates to drive continuous improvement and prevent recurrence.

Can I use this incident response framework for service degradations instead of full outages?

Yes, the incident response framework applies to both production outages and service degradations. It provides structured severity classification, triage steps, mitigation guidance, and communication workflows scaled to the detected incident's impact.

What's the best way to communicate incident status updates to internal teams and customers?

Incident status communications are coordinated through the response framework by the incident commander, ensuring structured mitigation updates are published to SRE, product leads, and affected customers throughout the event lifecycle.