SkillVaultskills Browse all 1,000+ skills

Reliability · Version 1.4.0 · Reviewed 2026-08-02

Operational Runbook Author

Reduce production risk in runbook structure and decision point design with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Writes runbooks that work at 3am: explicit preconditions, decision points, verification, and a defined escalation boundary.

₹299 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools, with a raw SKILL.md fallback for every other compatible IDE or agent.

See the complete graphical installation and usage guide

What this skill helps you do

  • Runbook structure
  • Decision point design
  • Escalation boundary

How Operational Runbook Author works

You provide

Incident notes, alert definitions, and prior variants

It inspects

Where a responder must branch and what discriminates

It decides

Ordered steps with an explicit escalation boundary

You verify

A responder unfamiliar with the system completes it

What it checks first

Operational Runbook Author writes runbooks that work at 3am: explicit preconditions, decision points, verification, and a defined escalation boundary. Use it when the work involves Runbook structure, Decision point design, Escalation boundary.

  1. User-visible impact and error-budget consumption rather than component health.
  2. Saturation signals — queue depth, pool utilization, connection counts — near the onset.
  3. Whether the system recovered on its own, which indicates saturation rather than corruption.
  4. The blast radius and what boundary should have contained it.

Failure modes it recognizes

  • Retry amplification turning a partial failure into a total outage.
  • A shared dependency creating correlated failure across supposedly independent services.
  • Slow resource exhaustion invisible until a hard limit is crossed.
  • A rollback blocked by an incompatible migration.

Answers it will reject

  • Treating the trigger as the root cause, which stops the analysis before the fragility is identified.
  • Adding a runbook step where a boundary would remove the failure mode.
  • Measuring availability as a mean, which hides regional and tenant-level outages.

Decision rules it applies

  • Stabilize user impact before completing diagnosis.
  • Bound every retry with a budget, jitter, and a circuit breaker.
  • Prefer removing a failure mode over detecting it faster.

Evidence it asks for

  • Record time-to-detect, time-to-mitigate, and time-to-resolve separately.
  • Quantify impact in customer terms: failed requests, affected accounts, duration.
  • Verify recovery with the same signal that detected the failure.

The method inside

  1. Turn runbook structure into explicit functional requirements and quality-attribute constraints.
  2. Model the critical path, state, trust, and failure boundaries that govern decision point design.
  3. Compare viable designs for escalation boundary against weighted constraints and operational ownership.
  4. Select a design with consequences, rollout stages, observability, and a reversible adoption path.

Deliverables

  • Runbook structure assessment
  • Decision point design decision and action plan
  • Escalation boundary verification checklist

Evidence requirements

  • User-visible symptoms and SLO impact
  • Timeline, telemetry, deploys, and dependency state
  • Current mitigations and operational constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Turn our incident notes into a runbook for the on-call rotation.

Expected output

Notes describe what happened once; a runbook must handle the variants. Add the discriminating check at each branch so a responder can tell which case they are in, and state the escalation point explicitly, since the most expensive runbook failure is someone continuing past their confidence...

Boundaries and compatibility

Ideal for

  • Runbook structure: produce a decision or artifact grounded in supplied evidence.
  • Decision point design: produce a decision or artifact grounded in supplied evidence.
  • Escalation boundary: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Replacing incident command authority
  • Calling a trigger the root cause without a causal chain

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.