Runbooks

A good runbook lets a competent responder do the right thing without improvising under stress.

Context

Runbooks convert operational knowledge into executable procedures. They are not long theory documents. They are concise operational guides for situations where time, clarity, and safety matter more than perfect prose.

In a lifecycle-aware system, runbooks should encode the same release boundaries the team reviewed earlier. For brownfield systems, that often means explicit rollback, fail-closed behavior, and coexistence-safe fallback steps.

Inputs

• incident-playbook -- produced by the preceding skill in the lifecycle
• monitoring-config -- produced by the preceding skill in the lifecycle
• ci-cd-pipeline -- produced by the preceding skill in the lifecycle

Process

Step 1: Define the Trigger and Owner