incident-response-commander

Coordinate incident response for production outages with runbooks and severity frameworks.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill incident-response-commander-coreymaypray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response-commander
Source: https://github.com/coreymaypray/sloth-skill-tree/tree/main/plugins/maycrest-secure/skills/incident-response-commander
Command: npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill incident-response-commander-coreymaypray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and standardize incident response for production outages, reducing chaos and restoring service with structured, repeatable processes.

Core Features & Use Cases

  • Define severity frameworks (SEV1-SEV4) and on-call rotations to ensure timely response
  • Create executable runbooks for common failure modes across Corey's stack (Supabase, Vercel, Stripe)
  • Facilitate blameless post-mortems, timelines, impact statements, and action-item tracking

Quick Start

Initiate an incident response plan for a SEV1 outage using defined roles, runbooks, and on-call rotations

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 incident response for a production outage?

Coordinate incident response by applying severity frameworks, defined on-call roles, and executable runbooks to restore service during production outages. This standardizes the process to reduce chaos and ensure timely, repeatable resolutions.

What is a blameless post-mortem and how does it work for outages?

A blameless post-mortem is a structured review process that facilitates timelines, impact statements, and action-item tracking after an incident. It focuses on systemic issues rather than individual fault to improve future reliability.

How do I create executable runbooks for common failure modes?

Create executable runbooks for common failure modes by documenting standardized, step-by-step resolution procedures for your specific stack components like Supabase, Vercel, and Stripe. This ensures on-call engineers can quickly restore service.

Can I use this incident response framework for a small engineering team?

Yes, you can use this incident response framework for a small engineering team. It is specifically designed to apply severity frameworks, on-call rotations, and stakeholder communications within small team environments.

What is the best way to define severity levels for production incidents?

The best way to define severity levels is to implement a structured SEV1 through SEV4 framework. This categorizes incidents by impact to ensure appropriate on-call escalation policies and timely stakeholder communications.