incident-commander

Coordinates incident response with structured roles, escalation paths, and phased workflows.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill incident-commander-patasse97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-commander
Source: https://github.com/Patasse97/claude-skills/tree/main/engineering-team/incident-commander
Command: npx skills add https://github.com/Patasse97/claude-skills --skill incident-commander-patasse97

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Incident Commander Skill provides a centralized, playbook-driven approach to leading incident response, coordinating cross-functional teams, and maintaining clear communication during outages.

Core Features & Use Cases

  • Role orchestration: defines IC, communications lead, operations lead, scribes, SMEs, and stakeholder ownership to reduce confusion.
  • Template-driven communications: status updates, executive summaries, and customer messages to ensure consistent messaging.
  • Runbook-guided response: pre-built playbooks for detection, triage, mitigation, and post-incident review.
  • Cross-team collaboration: war room orchestration, escalation paths, and handoffs across multiple teams for complex incidents.

Quick Start

Establish the incident command post and begin coordinated response using the included templates and runbooks.

Frequently Asked Questions about incident-commander

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

FAQPage Schema
How do I coordinate incident response across multiple teams during an outage?

Incident response coordination across multiple teams requires structured role assignment for the incident commander, operations lead, and scribes. This Skill enforces role orchestration, escalation paths, and war room coordination to reduce confusion during cross-functional outages and minimize mean time to resolution.

What is the best way to structure incident communications for executives and customers?

Incident communications are structured using pre-built templates for status updates, executive summaries, and customer messages. This Skill provides template-driven messaging to ensure consistent, accurate communication across all stakeholder levels during an active outage.

How do I automate incident runbooks for detection, triage, and mitigation?

Incident runbooks are automated using pre-built playbooks that guide detection, triage, mitigation, and post-incident review. This Skill enforces phased workflows with time-based triggers to standardize the response process and reduce manual overhead.

Does this incident command approach work for complex multi-team escalations and war rooms?

Incident command for complex multi-team escalations is supported through war room orchestration, structured escalation paths, and cross-team handoffs. It is designed for organizations managing on-call rotations and coordinating multiple teams during severe outages.

How do I generate post-incident review outputs after resolving an outage?

Post-incident review outputs are generated through the runbook-guided response workflow, which includes a dedicated post-incident review phase. This Skill captures scribe notes and phased timelines to produce structured post-mortem documentation after mitigation.

What roles need to be assigned when establishing an incident command post?

Incident command post roles include the incident commander, communications lead, operations lead, scribes, subject matter experts, and stakeholder owners. This Skill enforces clear role assignment to eliminate confusion and streamline accountability during response.