incident-commander

Coordinate structured incident response for production outages.

15|5|Updated May 17, 2026
One-click install
npx skills add https://github.com/cropsgg/skills --skill incident-commander-cropsgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-commander
Source: https://github.com/cropsgg/skills/tree/main/skills/planning/incident-commander
Command: npx skills add https://github.com/cropsgg/skills --skill incident-commander-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Active incident response protocol for production outages. Provides severity classification, communication templates, rollback decision trees, and post-incident report generation. Distinguishes between incident response (during) and postmortem (after). Enforces structured command-and-control to prevent panic-driven fixes.

Core Features & Use Cases

  • Phase-based workflow: triage, evidence preservation, decision-tree guided rollbacks/mitigations, communication rhythm, and postmortem handoff.
  • Templates for incident communications and postmortems to ensure reproducibility and clarity.
  • Use Cases: Active outages and post-incident reviews across teams and environments.

Quick Start

Activate incident-commander during an outage to begin structured triage and autonomous coordination.

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 for a production outage without panic-driven fixes?

Structured incident response enforces phase-based procedures, evidence preservation, and clear communication templates to coordinate production outages. It guides triage, rollback decisions, and mitigation systematically to prevent panic-driven fixes during active incidents.

What is the difference between active incident response and a postmortem?

Incident response manages active outages through triage, rollback decision trees, and real-time communication, while a postmortem generates post-incident reports after resolution. This structured protocol distinguishes between immediate command-and-control during the event and documentation afterward.

How do I use a rollback decision tree during an active incident?

A rollback decision tree guides mitigation choices during active incidents by enforcing evidence preservation and phase-based procedures. It structures the evaluation process to determine when to execute rollbacks versus other mitigations within the incident response workflow.

Can this incident response protocol work across different teams and environments?

Yes, this incident response protocol applies to active outages and post-incident reviews across teams and environments. It provides severity classification and standardized communication templates to ensure reproducibility and clarity regardless of the specific infrastructure.

What is the best way to structure communication during an SRE incident?

The best way to structure SRE incident communication is using standardized templates that enforce a clear communication rhythm. This ensures reproducibility and clarity across severity levels during active outages and post-incident reviews.

When should I start evidence preservation during an incident response?

Evidence preservation should start immediately during the triage phase of incident response. The structured protocol enforces collecting and securing evidence early in the active outage workflow to support accurate postmortem documentation and rollback decisions.