skills.rest
augustoheiss
augustoheissCOMMUNITY
Explore all skills by this author →
GitHub

agency-incident-response-commander

Coordinate production incident response with roles, runbooks, and post-mortems.

Updated Feb 11, 2026
Search Tags:#on-call#sre#runbooks#incident#response#blameless
One-click install
npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-incident-response-commander-augustoheiss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-incident-response-commander
Source: https://github.com/augustoheiss/LogicDefense/tree/main/.gemini/skills/agency-incident-response-commander
Command: npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-incident-response-commander-augustoheiss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident response coordination and on-call design to reduce outage impact and improve reliability across engineering teams.

Core Features & Use Cases

  • Structured incident command with defined roles (Incident Commander, Communications Lead, Technical Lead, Scribe) and severity framework (SEV1–SEV4).
  • Runbooks, on-call rotations, SLO/SLI tracking, and post-mortem facilitation to drive reliability.
  • Use Case: During a production outage, teams coordinate actions, communicate effectively, and complete a blameless post-mortem with actionable improvements.

Quick Start

Initiate the incident response protocol for a sev2 outage and assign the Incident Commander, Communications Lead, Technical Lead, and Scribe.

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 coordinate incident response during a production outage?▼

Coordinate incident response by assigning structured roles like Incident Commander, Communications Lead, Technical Lead, and Scribe to manage production outages. The framework establishes severity levels from SEV1 to SEV4 to guide actions.

What is a blameless post-mortem and how do I facilitate one?▼

A blameless post-mortem is a facilitated review process focusing on systemic issues rather than individual fault after an incident. It produces traceable artifacts and actionable improvements to drive team reliability.

Can I use this to manage on-call rotations and track SLOs?▼

Yes, you can manage on-call rotations and track SLOs/SLIs during outages. The system coordinates runbook execution and on-call processes across distributed systems to reduce outage impact.

How do I assign incident response roles for a SEV2 outage?▼

Assign incident response roles for a SEV2 outage by initiating the protocol to designate the Incident Commander, Communications Lead, Technical Lead, and Scribe. This structure ensures coordinated actions.

What is the best way to execute runbooks during an outage?▼

Execute runbooks during an outage through a structured incident command framework that manages alerts and escalations. This ensures reliable execution aligned with severity levels and on-call processes.

Related Skills

Explore More Software Engineering Skills→
nksethnkseth

sre-engineer

Define SLOs, SLIs, and error budgets to quantify service reliability.

Community
Advanced
ambroviaambrovia

retro

Log project observations, failures, and successes into structured JSONL files.

Official
Advanced
XiaoPuOuOXiaoPuOuO
1

oncall-sre-operations

Automate on-call incident triage, severity routing, runbook selection, and escalation for AI SaaS services.

Community
Advanced
marquesfelipmarquesfelip

incident-response-playbooks

Standardize incident response workflows from detection to post-mortem.

Community
Advanced