agency-incident-response-commander

Coordinates production incident response, post-mortems, and SLO tracking for engineering teams.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-incident-response-commander-immamdouhaboammar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-incident-response-commander
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/engineering-incident-response-commander
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-incident-response-commander-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production incidents often devolve into chaotic, uncoordinated firefighting with unclear ownership, poor stakeholder communication, and no follow-through on root causes. This Skill provides a structured incident command framework that turns outages into organized response efforts with defined roles, severity classification, and blameless post-mortems. ## Core Features & Use Cases - Structured Incident Response: Establishes SEV1–SEV4 severity classification, assigns roles (Incident Commander, Communications Lead, Technical Lead, Scribe), and enforces time-boxed troubleshooting with fixed communication cadences. - Post-Mortem Facilitation: Generates blameless post-mortem documents with timelines, 5 Whys root cause analysis, and tracked action items with owners and deadlines. - SLO/SLI & On-Call Design: Defines error budgets, burn-rate alerts, on-call rotation schedules, escalation policies, and runbook templates with tested remediation steps. - Use Case: Your payment API starts returning 5xx errors at 2 AM. The Skill guides you through declaring a SEV1, assigning roles, executing a rollback runbook, communicating with stakeholders every 15 minutes, and producing a complete post-mortem within 48 hours. ## Quick Start Ask the agent to help you declare and coordinate a response for a production outage affecting your checkout service, including severity classification and stakeholder communication.

Frequently Asked Questions about agency-incident-response-commander

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

FAQPage Schema
How do I structure a production incident response process?▼

Start by classifying severity using a SEV1–SEV4 matrix, then assign explicit roles: Incident Commander, Communications Lead, Technical Lead, and Scribe. Timebox investigation hypotheses to 15 minutes each and send stakeholder updates at fixed intervals based on severity level.

How to run a blameless post-mortem after an outage?▼

Schedule the post-mortem within 48 hours while memory is fresh, walk through the incident timeline as a group, and use 5 Whys analysis to find systemic causes rather than blaming individuals. Every action item needs a named owner, priority, and deadline tracked to completion.

What is the difference between SLO, SLI, and SLA?▼

An SLI is the measured indicator (e.g., request success rate), an SLO is the internal target for that indicator (e.g., 99.95% over 30 days), and an SLA is the contractual commitment to customers. SLOs define error budgets that trigger reliability work when burned.

How do I design an on-call rotation that prevents burnout?▼

Use weekly rotations with at least 4 engineers, limit consecutive on-call weeks to 2, and require a 2-week shadow period for new engineers. Track pages per shift and treat more than 5 pages per week as a signal to fix noisy alerts, not the people.

When should an incident be escalated to a higher severity?▼

Escalate when impact scope doubles, when no root cause is found after 30 minutes for SEV1 or 2 hours for SEV2, when paying customers report the issue, or when any data integrity concern exists. Data loss risk always triggers immediate SEV1 classification.