# Agent Workflow Approval Template

A static Goal Contract template for reviewing coding-agent work before execution. Use it to make outcome, blast radius, tool authority, validation, and stop conditions explicit.

## Core rule

Approve the workflow before the worker starts. A coding agent should not discover its own authority while it is already mutating the repo.

## 1. Outcome

One sentence describing the repo change the agent is allowed to complete. If the desired outcome changes, the run returns to review before continuing.

Template line:

> The agent is approved to: [specific outcome].

## 2. Approved blast radius

Name the exact repos, branches, directories, packages, services, files, and forbidden areas. Do not leave scope expansion to the worker's judgment.

Template line:

> Allowed scope: [paths/services]. Forbidden scope: [paths/secrets/deploys/customer data/etc.].

## 3. Tool and MCP permissions

List allowed shell commands, MCP servers, external services, write-capable tools, and anything that requires a new approval before use.

Template line:

> Allowed tools: [read/write/execute/external-send]. Stop before using: [unapproved tools].

## 4. Validation evidence

Define the checks that prove the run succeeded: tests, build, lint, screenshots, dry runs, manual acceptance steps, or deploy previews.

Template line:

> Required evidence: [commands/screenshots/review steps]. Failure handoff: [what to report].

## 5. Stop conditions

State the conditions that require the agent to stop and return to review instead of improvising: scope drift, failing checks, secrets, migrations, deploys, or unclear requirements.

Template line:

> Stop if: [conditions]. Return to reviewer with: [evidence and proposed next step].

## 6. Reviewer notes

Capture what the human reviewer changed, approved, rejected, or postponed before execution so later PR review can compare the final diff to the original intent.

Template line:

> Reviewer approved: [date/person]. Notes: [edits, rejected scope, follow-ups].

## Where Caskade goes beyond the template

This resource gives you the static approval shape. Caskade turns the shape into a live review surface: annotate the plan, iterate with teammates, keep the final diff consistent with the approved intent, and preserve the evidence trail.

Bring a real workflow: https://caskade.dev/?utm_source=resource&utm_medium=markdown&utm_campaign=agent-workflow-approval#access