Review a runbook for missing failure paths

A runbook is incomplete when it describes only the happy path. Check prerequisites, stop conditions and recovery evidence before relying on it.

Bound the operating task

Provide the relevant records and define what is a draft recommendation versus an approved action. Keep original records intact and ask for an output manifest so you can find the result. Start with file generation and human review before adding any external action through a connected tool. A useful operations deliverable should make exceptions and missing information visible.

Inputs for this workflow: The current runbook and known failure examples.

Work through the task

1. Identify each step’s success evidence.
2. List what to do when that evidence is absent.

A brief you can adapt

Write runbook-review.md with step, ambiguity, failure mode and proposed clarification. Mark commands needing owner verification.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Walk through one safe failure scenario using the revised instructions.

Where this approach can fail

Do not execute production repair commands merely because they appear in the document being reviewed.

For the related desktop setup, see review results.