Incident Response Commander

Coordinate production incident response with roles, severity matrices, and communication cadences.

Updated Apr 16, 2026

Search Tags:#post-mortem #on-call #runbooks #slo #incident #response #sli

Ready to run

npx skills add https://github.com/jc180105/.opencode --skill incident-response-commander-jc180105

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Incident Response Commander
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/engineering-incident-response-commander
Command: npx skills add https://github.com/jc180105/.opencode --skill incident-response-commander-jc180105

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident management teams struggle to coordinate rapid responses, artifacts, and learning after outages. This Skill provides a structured framework to handle production incidents from detection to post-mortem, ensuring reliable systems and calmer teams.

Core Features & Use Cases

Establish severity classifications (SEV1–SEV4) with clear escalation triggers and defined response cadences.
Coordinate real-time incident response with roles: Incident Commander, Communications Lead, Technical Lead, and Scribe.
Build and maintain runbooks, SLO/SLI frameworks, game days, and blameless post-mortems to drive continuous reliability.
Align on-call rotations and tooling integrations to support scalable incident readiness.

Quick Start

Initiate a structured incident response plan for a simulated production outage and outline roles, runbooks, and communication cadences.

Frequently Asked Questions about Incident Response Commander

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

FAQPage Schema

How do I coordinate a production incident response with structured roles?▼

Coordinate production incident response by assigning structured roles like Incident Commander, Communications Lead, Technical Lead, and Scribe to manage real-time resolution. This framework enforces mandatory deliverables and communication cadences to ensure reliable incident management.

What's the best way to establish severity classifications for on-call escalations?▼

Establish severity classifications by defining SEV1 through SEV4 levels with clear escalation triggers and defined response cadences. This structured matrix guides timely incident management and dictates the required communication frequency for each severity.

How does a blameless post-mortem work after a production outage?▼

A blameless post-mortem works by guiding teams through structured learning after an incident without assigning fault. It focuses on reviewing the response, updating runbooks, and refining SLO/SLI frameworks to drive continuous reliability.

How do I build SLO and SLI frameworks to improve incident readiness?▼

Build SLO and SLI frameworks by aligning on-call rotations, runbooks, and tooling integrations to measure service reliability. These frameworks support scalable incident readiness and provide objective metrics to trigger response actions during outages.

Can I use this to simulate a production outage for a game day?▼

Yes, you can simulate a production outage for a game day by initiating a structured incident response plan. The framework outlines roles, runbooks, and communication cadences to practice real-time resolution and calmer team coordination.

What is a structured command framework for incident management?▼

A structured command framework for incident management is a system that coordinates response from detection to post-mortem. It enforces scripted severity matrices, mandatory deliverables, and communication cadences to turn outage chaos into reliable resolution.