Runbook | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Repeatable runbook and troubleshooting instructions.

Start with: Procedure steps, expected results, failures and escalation contacts.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Define when the procedure should be used, who may perform it and what prerequisites or access are needed.
Write ordered actions with the expected result after each consequential step. Provide a path for common failures.
Specify recovery, escalation and the evidence needed for a useful handoff without embedding real credentials or contact details.
Return a repeatable Markdown runbook. Validate the logic against supplied examples and distinguish documented steps from steps actually tested.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Document ownership and repeatable work.

Possible success measures: Cycle time, rework, first-pass completion. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: runbook
description: "Prepare repeatable runbook and troubleshooting instructions. Use for this workflow with supplied business information."
---

# Runbook

## Inputs and purpose

Use this workflow to prepare: Repeatable runbook and troubleshooting instructions.

Start with: Procedure steps, expected results, failures and escalation contacts.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Define when the procedure should be used, who may perform it and what prerequisites or access are needed.

2. Write ordered actions with the expected result after each consequential step. Provide a path for common failures.

3. Specify recovery, escalation and the evidence needed for a useful handoff without embedding real credentials or contact details.

4. Return a repeatable Markdown runbook. Validate the logic against supplied examples and distinguish documented steps from steps actually tested.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Document ownership and repeatable work.

Possible success measures: Cycle time, rework, first-pass completion. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).