Claude: draft a support runbook with clear stop conditions

What you will make

A practical Claude guide to draft a support runbook with clear stop conditions. Use the sample input and prompt, then check the result. Use a fictional support-document review as the practice setting. Keep passages and your interpretation in separate output fields.

Prepare the source and scope

Provide an approved procedure and the service owner's escalation path. Distinguish observation from actions that modify the service. Open Claude and start a focused conversation, or use the appropriate existing project for recurring work.

Try this prompt

In Claude, provide the prepared input, then send the following request. For real work, replace fictional details with approved facts.

Turn these notes into a runbook with prerequisites, observations, decision points and escalation. Label state-changing steps and preserve the existing authorization conditions.

Review the result

Walk through a fictional incident and check that each branch leads to a defined next step or stop. Record each correction and its supporting source.

If the answer is wrong or incomplete

A neat sequence can omit rollback or ownership. Review those gaps with the service owner before operational use. Put the source excerpt and the request in separate labeled blocks. For longer reviews, retain paragraph labels so corrections remain traceable.

Practice and completion check

Repeat with one incomplete input. Check the answer against the review criteria, remove unsupported claims and save the prompt with its source version. This workflow has not been verified in a customer deployment.