Use Autohand Code to turn a manual runbook into scripts, checks, rollback notes, and operator-friendly output.
Convert manual operational steps into a repeatable workflow
Operations Delivery and operations Operate Workflow
autohand -p "Turn this manual runbook into an automated workflow with checks and rollback notes"
A repeatable runbook workflow with commands, safety gates, and verification steps.
Automate a runbook with Autohand Code is an operations workflow that converts manual recovery, release, or maintenance steps into repeatable commands with checks, rollback notes, and operator output. ### At a glance | Question | Answer | | --- | --- | | Best for | incident runbooks, release chores, environment setup, data repair steps, and recurring operational tasks | | Primary inputs | Current runbook steps, commands, required access, and expected outputs; Preconditions, approval steps, rollback path, and known failure modes; Target environment, dry-run behavior, and logs operators should see | | Autohand Code returns | A repeatable runbook workflow with commands, safety gates, and verification steps. | | Avoid when | the manual process is still unsafe, undocumented, or missing approval gates | ### How Autohand Code handles this workflow 1. Turns manual steps into ordered commands, scripts, or checklist-backed automation. 2. Adds preflight checks before any state-changing action. 3. Keeps rollback and failure messages visible to the operator. 4. Validates dry-run behavior first, then records the production-safe execution path. ### Best inputs - Current runbook steps, commands, required access, and expected outputs - Preconditions, approval steps, rollback path, and known failure modes - Target environment, dry-run behavior, and logs operators should see ### Strong prompt autohand -p "Turn this manual runbook into an automated workflow with checks and rollback notes" ### Autohand Code CLI options - Run `autohand -p "Turn this manual runbook into an automated workflow with checks and rollback notes"` with the existing runbook text. - Use `--dry-run` and `--restricted` for the design pass before allowing state-changing commands. - When `slash_goal` is enabled, use `/goal` to track preflight, implementation, dry-run, and rollout verification as one operational objective. ### Review before accepting The automation should show preconditions, idempotent steps where possible, dry-run output, rollback notes, and operator-facing errors. ### Source and validation signals Autohand AI maintains this workflow as first-party product guidance for Autohand Code. Use the [Autohand CLI Playbook](https://github.com/autohandai/code-cli/blob/main/docs/AUTOHAND_PLAYBOOK.md), [CLI reference](/docs/working-with-autohand-code/cli-reference.html), and [configuration reference](https://github.com/autohandai/code-cli/blob/main/docs/config-reference.md) when choosing between interactive mode, command mode, auto-mode, feature-enabled /goal, /settings, skills, MCP, and permission settings. The related resources below link to product docs and tutorials for the workflow, and the final answer should name repository-specific files, commands, outputs, or docs that a reviewer can verify. ### Frequently asked questions ### What is Automate a runbook with Autohand Code? Automate a runbook with Autohand Code is an operations workflow that converts manual recovery, release, or maintenance steps into repeatable commands with checks, rollback notes, and operator output. ### When should a team use Automate a runbook? Use it when the same operational task is repeated enough that missed steps, unclear output, or slow handoff create risk. ### What evidence should reviewers check for Automate a runbook? The automation should show preconditions, idempotent steps where possible, dry-run output, rollback notes, and operator-facing errors.
Guide Runbook Automation Convert repeatable operational work into safe automation. /docs/guides/sre/runbook-automation.html Guide Incident Response Keep response steps, rollback paths, and operator output explicit. /docs/guides/sre/incident-response.html Guide Auto Mode Use bounded autonomous loops for repeatable checks and fixes. /docs/guides/auto-mode.html