Incident Escalation Playbook Example
This document explains the Incident Escalation example built with the implementation-playbook skill. Unlike the approval-oriented access-request example, this one focuses on an operations workflow that assembles an escalation packet based on severity and impact.
What It Demonstrates
- separate
draft / validation / escalation / activitystores - an explicit state machine with severity-driven rules
- separation between validation issues and UI wording
- activity logs derived from domain events
- invalidating a stale escalation result when severity changes after success
Route
text
/patterns/implementation-playbook/incident-escalationKey Files
text
example/src/pages/patterns/implementation-playbook/incident-escalation/
├── IncidentEscalationExample.tsx
├── IncidentEscalationExamplePage.tsx
├── contexts/
│ └── IncidentEscalationContexts.tsx
├── business/
│ ├── incidentDraft.ts
│ ├── incidentValidation.ts
│ ├── incidentEscalationPacket.ts
│ ├── incidentActivity.ts
│ ├── incidentStateMachine.ts
│ └── incidentBusiness.ts
├── handlers/
│ ├── IncidentEscalationHandlers.tsx
│ ├── incidentHandlerSupport.ts
│ ├── useIncidentDraftHandlers.tsx
│ └── useIncidentSubmissionHandlers.tsx
├── actions/
│ └── useIncidentEscalationActions.ts
├── hooks/
│ └── useIncidentEscalationData.ts
└── views/
└── IncidentEscalationView.tsxState Machine
mermaid
stateDiagram-v2
[*] --> idle
idle --> validating: escalation_requested
validating --> blocked: validation_failed
validating --> assembling: validation_passed
assembling --> ready: packet_ready
ready --> idle: draft_changed
blocked --> idle: draft_changed
idle --> idle: prefill_loaded / resetWhy This Example Matters
This example proves that the implementation-playbook also works for operations and incident response workflows.
- escalation-packet creation instead of quote generation
- severity, affected-user, and channel rules instead of pricing
- operational checklist and escalation target computation
The skill is not limited to form-processing examples.
Verification Focus
- sev1 incidents without statuspage block submission
- valid incidents assemble an escalation packet
- changing severity after success returns the workflow to idle
- reset restores the baseline state