Runbook Builder | Agent Runbooks

01

Outcome / Objective

Start with what should exist when the work is done.

Desired outcomeBe specific about the result, not just the activity.

02

Context

Give the agent the facts it needs.

Project contextURLs, source access, target user, technology stack, previous work, and assumptions.

03

Job / Scope

Define the work. One task or phase per line.

Tasks to performKeep each task tied to the outcome.

04

Constraints / Preserve

Protect the things that already work.

Boundaries and exclusionsState what must remain and what the agent must not do.

05

Execution Strategy

Choose how the work should proceed.

Execution approachFor example: inspect first, reuse components, validate affected behavior.

06

Autonomy

Allow routine decisions within the defined scope.

Inspect relevant files and existing artifactsBrowse and research relevant sourcesChoose reversible implementation detailsModify source within the agreed scopeRun relevant tests and validationInstall necessary dependenciesCreate files required for the deliverableReorganize noncritical content

Additional permissionsOptional. Approval gates take precedence.

07

Approval Gates

Require explicit approval before consequential actions.

Additional approval gatesOptional. Name the exact action requiring approval.

08

Return Conditions

Define when the agent should hand control back.

The requested work and relevant validation are complete.The next necessary action requires explicit approval; first prepare a concrete, reviewable result where possible.Required access is unavailable and independent work is exhausted.A material decision cannot safely be inferred.Remaining work would exceed the agreed scope.Meaningful progress is blocked after the recovery policy has been applied.

Additional return conditionsOptional. Avoid stopping for routine authorized decisions.

09

Failure / Recovery

Preserve progress when something goes wrong.

Do not repeat the same failed operation without new evidence; attempt at most one reasonable alternative when appropriate.Preserve existing working behavior when uncertainty exists.Continue independent work when one task is blocked.Document reasonable assumptions and continue when risk is low.Stop before irreversible actions or actions requiring approval.Report blockers and incomplete work clearly; never imply success without evidence.Resume from completed work rather than restarting it.Do not expand scope to work around a localized problem.

Additional recovery instructionsOptional. Include a project-specific fallback or resume point.

10

Definition of Done

Make completion objectively checkable.

Acceptance criteriaOne criterion per line. Include the deliverable and how it is validated.

11

Resource Strategy

Behavioral guidance, not a prediction of usage.

ConservativePrefer minimal tool calls and targeted research. Reuse existing architecture, validate the affected behavior, and stop when the requested outcome is satisfied.BalancedUse enough research, reasoning, and validation to reliably achieve the objective. Avoid unnecessary exploration and expansion.ThoroughInvestigate relevant alternatives, validate edge cases, and review evidence more deeply where this improves the result. Keep all work within the agreed scope.

Define the job.

Your runbook