incident-commander

Guide incident response with severity levels and phased resolution workflows.

5|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/latestaiagents/agent-skills --skill incident-commander-latestaiagents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-commander
Source: https://github.com/latestaiagents/agent-skills/tree/main/plugins/devops-sre/skills/incident-response/incident-commander
Command: npx skills add https://github.com/latestaiagents/agent-skills --skill incident-commander-latestaiagents

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework and clear guidance for managing critical incidents, ensuring efficient coordination, communication, and resolution to minimize impact.

Core Features & Use Cases

  • Incident Triage & Severity: Define and assign severity levels (SEV1-SEV4) for accurate response prioritization.
  • Workflow Management: Guides through distinct phases: Detection, Mobilization, Investigation, Mitigation, and Resolution.
  • Role Definition: Clearly outlines responsibilities for key roles like Incident Commander (IC), Tech Lead, and Comms Lead.
  • Communication Templates: Provides ready-to-use templates for incident declarations, status updates, and resolution announcements.
  • Use Case: When a critical service outage occurs (SEV1), this skill helps you immediately declare the incident, assemble the right team, establish communication channels, and systematically work towards restoring service while keeping stakeholders informed.

Quick Start

Use the incident-commander skill to guide the response for a critical production issue.

Frequently Asked Questions about incident-commander

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

FAQPage Schema
How do I manage incident response for a critical production outage?

Incident response for a production outage requires structured workflows spanning Detection, Mobilization, Investigation, Mitigation, and Resolution to coordinate teams and systematically restore service.

What is an incident commander role during service degradation?

An incident commander is a defined role responsible for coordinating the response to service degradation, assigning responsibilities to Tech and Comms Leads, and guiding phased resolution workflows.

How do I assign severity levels during critical incident triage?

Assign severity levels during incident triage by evaluating impact across defined categories (SEV1-SEV4) to accurately prioritize response efforts and mobilize appropriate resources for mitigation.

Can I use structured communication templates for incident status updates?

Structured communication templates can be used to standardize incident declarations, deliver consistent status updates, and announce resolutions to stakeholders throughout the outage management lifecycle.

What is the best way to structure outage management workflows for SEV1 incidents?

The best way to structure outage management for SEV1 incidents is to follow defined communication protocols, establish clear role assignments, and systematically progress through phased resolution workflows.

When do I need a formal incident management process for production issues?

A formal incident management process is needed when production issues cause critical service outages or degradations, requiring immediate triage, structured role assignment, and stakeholder communication protocols.