Incident Commander Skill

Coordinates incident response with structured framework, escalation paths, and post-incident artifacts.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/theandyalvarez7-ruby/claude-skills --skill incident-commander-skill-theandyalvarez7-ruby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Incident Commander Skill
Source: https://github.com/theandyalvarez7-ruby/claude-skills/tree/main/engineering-team/incident-commander
Command: npx skills add https://github.com/theandyalvarez7-ruby/claude-skills --skill incident-commander-skill-theandyalvarez7-ruby

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Coordinating incident response across multiple teams can be chaotic and error-prone without a clear owner, shared playbooks, and unified communications.

Core Features & Use Cases

  • Role orchestration: Define and assign Incident Commander, Communications Lead, Operations Lead, and Scribe to ensure clear ownership during incidents.
  • Template-driven communications: Pre-built status, executive, and customer communication templates to reduce noise and increase clarity.
  • Runbook integration: Generate actionable response runbooks and RCA frameworks for rapid containment and learning.
  • Post-incident analysis: Structured guidance for PIR generation and root cause analysis to accelerate learning and prevention.

Quick Start

Create the incident channel, assign IC, Communications Lead, and Scribe, then initiate the initial briefing.

Frequently Asked Questions about Incident Commander Skill

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

FAQPage Schema
How do I coordinate incident response across multiple engineering teams without losing track of ownership?

Incident command frameworks orchestrate multi-team triage by assigning clear roles like Incident Commander, Communications Lead, and Scribe. This structured approach provides an escalation path, initial actions, and post-incident artifacts to accelerate recovery and ensure unified communications.

What is the best way to structure stakeholder communications during an active site reliability incident?

Structured stakeholder communications during an SRE incident use template-driven formats for status, executive, and customer updates. This reduces noise and increases clarity by providing pre-built communication templates that ensure consistent messaging across engineering and operations.

How do I generate a post-incident report (PIR) and root cause analysis after a major outage?

Post-incident analysis provides structured guidance for PIR generation and root cause analysis. It outputs post-incident artifacts that accelerate learning and prevention by guiding you through RCA frameworks built into the incident response runbooks.

Can I use this incident command framework for SRE triage and escalation in my existing operations workflow?

Yes, this incident command framework supports SRE triage and escalation within existing operations workflows. It generates an actionable response runbook and escalation path that integrate with your engineering and operations teams to accelerate safe recovery.

What roles do I need to assign during an incident response to ensure clear ownership?

Incident response requires assigning an Incident Commander, Communications Lead, Operations Lead, and Scribe. Role orchestration ensures clear ownership during incidents by defining and assigning these specific responsibilities to coordinate rapid containment.

Why does multi-team incident response become chaotic and error-prone without a shared runbook?

Multi-team incident response becomes chaotic without a clear owner, shared playbooks, and unified communications. Template-driven runbooks solve this by providing actionable response frameworks and structured RCA guidance to coordinate fast, safe recovery.