Incident Commander Skill

Coordinate incident response runbooks and generate post-incident reviews.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/AgLyx3/My-Note-App-Not-Just-a-Note-App --skill incident-commander-skill-aglyx3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Incident Commander Skill
Source: https://github.com/AgLyx3/My-Note-App-Not-Just-a-Note-App/tree/main/.cursor/skills/engineering-team/incident-commander
Command: npx skills add https://github.com/AgLyx3/My-Note-App-Not-Just-a-Note-App --skill incident-commander-skill-aglyx3

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Incident Commander Skill provides a structured framework for managing technology incidents from detection through resolution and post-incident review, enabling faster, blameless, and well-documented responses.

Core Features & Use Cases

  • Automated severity classification and on-call routing
  • Timeline reconstruction and evidence-backed decision logging
  • PIR generation with multiple RCA frameworks and actionable learnings
  • Ready-made templates for status updates, executive briefs, and customer communications
  • Runbook integration and cross-team coordination for multi-service incidents

Quick Start

Use this skill during a live incident to establish command, classify severity, coordinate SMEs, and generate a post-incident review.

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 during a high-severity outage?

Incident response coordination uses a structured framework with defined Incident Commander roles and runbooks to establish command, route on-call personnel, and coordinate cross-team SMEs during multi-service outages.

What is the best way to automate blameless postmortem and PIR generation after resolving an incident?

Blameless postmortem generation reconstructs the incident timeline and logs evidence-backed decisions to automatically produce a Post-Incident Review (PIR) using multiple RCA frameworks for actionable learnings.

How do I classify incident severity and standardize communications during a live outage?

Incident severity classification standardizes communications by applying ready-made templates for status updates, executive briefs, and customer-facing notifications to ensure consistent, auditable updates.

Does this incident management framework work for high-stakes outages requiring executive briefs?

Yes, the framework is designed for high-stakes outages and multi-team incidents, providing standardized severity classification and ready-made executive brief templates to satisfy auditable incident management requirements.

When do I need a formal incident command runbook for managing technology incidents?

A formal incident command runbook is needed when managing high-severity outages that require structured severity routing, cross-team coordination, and auditable post-incident reviews to ensure fast, blameless resolution.

Can I use SRE runbooks to generate actionable learnings from a post-incident review?

Yes, SRE runbooks integrate with the incident command process to reconstruct timelines and generate PIRs using multiple RCA frameworks, translating evidence-backed decisions into actionable learnings.