# Incident Response

> Design incident response — runbooks, war rooms, postmortems, blameless culture — with explicit severity taxonomy, escalation paths, and communication rules.

- Skill: `quantumquirkxyz/incident-response` (Agent Skill)
- Install (CLI): `npx get-skill add quantumquirkxyz/incident-response`
- Raw SKILL.md: https://api.skillmd.com/api/skills/quantumquirkxyz/incident-response/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: quantumquirkxyz (https://skillmd.com/u/quantumquirkxyz)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/quantumquirkxyz/incident-response

---


## Contract

- Input: service inventory, on-call structure, communication channels, past incident history (optional).
- Output: incident response plan + runbook library + postmortem process.
- Scope: designs response process; does not execute incident command unless explicitly instructed.
- Rule: designs response process; does not execute incident command unless explicitly instructed.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.

## Provenance

| Question | Answer |
|---|---|
| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |
| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |
| What risk remains? | Subjective judgment calls, missing context, or external dependency failures


## Artifact

Emit `IncidentResponseArtifact` as both:
- JSON: `.agents/skills/platform/artifacts/incident-response/{identifier}.json`
- Markdown view: same filename with `.md` extension


# 
# 
# Incident Response

Design **incident response** — runbooks, war rooms, postmortems, blameless culture — with explicit severity taxonomy, escalation paths, and communication rules.

## Process

### 1. Severity taxonomy
- Severity levels (SEV1 / SEV2 / SEV3 / SEV4) with customer impact and SLA definitions.
- Time-to-acknowledge and time-to-resolve targets per level.
- Escalation matrix (on-call → secondary → manager → executive).
- Declaration authority (who can declare a SEV and how).

**Completion criterion:** severity taxonomy and escalation matrix documented.

### 2. Incident workflow
- Detection (alerts, user reports, synthetic monitors).
- Triage (initial assessment, severity assignment, owner assignment).
- Mitigation (rollback, feature flag kill, capacity increase, traffic shift).
- Resolution (root cause confirmed, fix deployed, monitoring verified).
- Communication cadence (status page, stakeholder updates, customer updates).

**Completion criterion:** incident workflow with time targets defined.

### 3. Runbooks
- Per-service runbooks (start/stop, health checks, known failure modes).
- Per-failure-mode runbooks (latency spike, error rate increase, data inconsistency).
- Rollback and restore procedures with verification steps.
- Escalation contacts and communication templates.

**Completion criterion:** runbook library with verification steps defined.

### 4. War room and incident command
- Incident commander (IC) responsibilities and decision authority.
- War room setup (video bridge, Slack channel, shared doc).
- Roles (IC, communications lead, technical lead, scribe).
- Communication rules (what to say, what not to say, cadence).

**Completion criterion:** incident command structure and communication rules defined.

### 5. Postmortem process
- Trigger (SEV1 / SEV2, or any SEV with > X minutes duration).
- Timeline reconstruction (logs, metrics, deployment history, chat).
- Root cause analysis (5 Whys, fault tree, contributing factors).
- Remediation items (immediate fix, preventive action, detection improvement).
- Action item tracking (owner, due date, verification).

**Completion criterion:** postmortem template with action item tracking defined.

### 6. Blameless culture
- Focus on systems and processes, not individuals.
- Psychological safety guidelines for postmortem participants.
- Recognition of effective response, not punishment for honest mistakes.
- Retrospective scheduling and cross-team sharing.

**Completion criterion:** blameless culture guidelines documented.

## Rules

- Rule: define severity by customer impact, not by team comfort.
- Rule: keep runbooks executable by any on-call engineer, not just the service author.
- Rule: require a postmortem for every SEV1 / SEV2; optional for lower severities.
- Rule: track remediation items in the same system as product work so they are visible and ship.
- Rule: conduct GameDays for critical runbooks so they stay fresh and accurate.

## Completion

- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
---
@include .agents/skills/platform/contract-base.xml
