# Teammate agent handoff

Blank template. Describe the actual state; no checks or task results are implied.
Guide: https://openscout.app/blog/handoff-not-the-chat
Builder: https://openscout.app/tools/agent-handoff-builder

## Goal

Concrete outcome:

## Acceptance

- Observable done-when checks:
- Human acceptance owner:

## Scope

- Files / surfaces in scope:
- Permitted actions:
- Constraints and excluded actions:

## Touched

- Repository and recipient's authorized access path:
- Base and head revisions:
- Changed files:
- Uncommitted diff / working-tree status, if applicable:

## Stopped

- Current state and when it was checked:
- Last accepted decision and its source:
- Existing work still running:
- Known failure or unanswered question:
- First useful next action:

## Next owner and return path

- Teammate who agreed to take the task:
- Original returned Scout reference, when available:
- Relevant broker / supported continuation path:
- Where the result should be returned:

## Evidence

- Exact checks, results, revision/environment and output references:
- Failed checks:
- Checks not run or not verified:
- Relevant specification and decisions:
- Access or context still missing:

## Recipient readback

- I can access:
- The revision I will inspect:
- My next action:
- The check I will use:
- The question or permission still needed:
- Where I will return the result:

Confirm access before dependent work begins. Inspect existing work before
launching another task. A brief does not transfer credentials, hidden context,
or ownership of a live harness session; it does not grant execution permissions.