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
1---2name: "incident-response"3category: "devops"4maturity: "stable"5version: "1"6description: "Design incident response — runbooks, war rooms, postmortems, blameless culture — with explicit severity taxonomy, escalation paths, and communication rules."7license: "MIT"8capabilities:9 - apply incident response methods within explicit devops boundaries10 - analyze design incident response — runbooks, war rooms, postmortems, blameless culture — with explicit severity taxonomy, escalation paths, and communication rules with assumptions, constraints, and failure modes11 - produce and validate a devops artifact with evidence, decisions, and next steps12outputs: "incident response plan + runbook library + postmortem process."13sideEffects: []14dependencies: []15stopCondition: "Incident response plan complete; runbook library defined; postmortem process documented."16risk: "medium"17trustTier: "3"18maxIterations: "6"19promptVersion: "2.0"20artifactType: "devops"21modelTier: "reasoning"22evaluators: ["behavioral", "regression"]23fixturesPath: .agents/skills/platform/fixtures/behavioral/incident-response.json24diataxis: "how-to"25tags: ["devops"]26compatibility: []27approvalRequired: "true"28approvalFor: []29metadata:30 source: https://skillmd.com/skills/quantumquirkxyz/incident-response31---3233## Contract3435- Input: service inventory, on-call structure, communication channels, past incident history (optional).36- Output: incident response plan + runbook library + postmortem process.37- Scope: designs response process; does not execute incident command unless explicitly instructed.38- Rule: designs response process; does not execute incident command unless explicitly instructed.39- Rule: documented standards override defaults; explicit project rules take precedence.40- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4142## Provenance4344| Question | Answer |45|---|---|46| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |47| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |48| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |49| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |50| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |51| What risk remains? | Subjective judgment calls, missing context, or external dependency failures525354## Artifact5556Emit `IncidentResponseArtifact` as both:57- JSON: `.agents/skills/platform/artifacts/incident-response/{identifier}.json`58- Markdown view: same filename with `.md` extension596061# 62# 63# Incident Response6465Design **incident response** — runbooks, war rooms, postmortems, blameless culture — with explicit severity taxonomy, escalation paths, and communication rules.6667## Process6869### 1. Severity taxonomy70- Severity levels (SEV1 / SEV2 / SEV3 / SEV4) with customer impact and SLA definitions.71- Time-to-acknowledge and time-to-resolve targets per level.72- Escalation matrix (on-call → secondary → manager → executive).73- Declaration authority (who can declare a SEV and how).7475**Completion criterion:** severity taxonomy and escalation matrix documented.7677### 2. Incident workflow78- Detection (alerts, user reports, synthetic monitors).79- Triage (initial assessment, severity assignment, owner assignment).80- Mitigation (rollback, feature flag kill, capacity increase, traffic shift).81- Resolution (root cause confirmed, fix deployed, monitoring verified).82- Communication cadence (status page, stakeholder updates, customer updates).8384**Completion criterion:** incident workflow with time targets defined.8586### 3. Runbooks87- Per-service runbooks (start/stop, health checks, known failure modes).88- Per-failure-mode runbooks (latency spike, error rate increase, data inconsistency).89- Rollback and restore procedures with verification steps.90- Escalation contacts and communication templates.9192**Completion criterion:** runbook library with verification steps defined.9394### 4. War room and incident command95- Incident commander (IC) responsibilities and decision authority.96- War room setup (video bridge, Slack channel, shared doc).97- Roles (IC, communications lead, technical lead, scribe).98- Communication rules (what to say, what not to say, cadence).99100**Completion criterion:** incident command structure and communication rules defined.101102### 5. Postmortem process103- Trigger (SEV1 / SEV2, or any SEV with > X minutes duration).104- Timeline reconstruction (logs, metrics, deployment history, chat).105- Root cause analysis (5 Whys, fault tree, contributing factors).106- Remediation items (immediate fix, preventive action, detection improvement).107- Action item tracking (owner, due date, verification).108109**Completion criterion:** postmortem template with action item tracking defined.110111### 6. Blameless culture112- Focus on systems and processes, not individuals.113- Psychological safety guidelines for postmortem participants.114- Recognition of effective response, not punishment for honest mistakes.115- Retrospective scheduling and cross-team sharing.116117**Completion criterion:** blameless culture guidelines documented.118119## Rules120121- Rule: define severity by customer impact, not by team comfort.122- Rule: keep runbooks executable by any on-call engineer, not just the service author.123- Rule: require a postmortem for every SEV1 / SEV2; optional for lower severities.124- Rule: track remediation items in the same system as product work so they are visible and ship.125- Rule: conduct GameDays for critical runbooks so they stay fresh and accurate.126127## Completion128129- the skill's completion criteria are explicitly checked130- the artifact is saved and validated131- any blockers or skipped validations are documented132- the next consumer is identified or the work is handed off133---134@include .agents/skills/platform/contract-base.xml