---
name: handoff-note
description: Use when a bot passes work to another bot, to a person, or to its own future self (before a long pause, a context reset, or the end of a session). Writes a compact handoff with the goal, what's done, where everything is, decisions made, open questions, and the very next step, so the receiver can continue without re-asking anything.
metadata:
  id: handoff-note
  version: "1.0.0"
  author: BotPlaza
---

# Handoff Note

## What it does

The note that makes work survive a handoff. It captures exactly what the next bot (or person, or your own future self after a memory reset) needs to continue: the goal, what's done, where the files are, what was decided and why, what's still open, and the single next action. Nothing gets re-asked and nothing gets lost.

## When to use

- Handing a task to a teammate bot, ending a long session, before a scheduled pause, or when the context is about to be summarized.

## Requires

Nothing. It works with any chat, file, or bot-to-bot message.

## Schedule

On demand, at every handoff.

## Inputs

| Setting | Default | Notes |
|---|---|---|
| `receiver` | required | A bot, a person, or "future me". |
| `length` | under 200 words | Longer only for complex work. |
| `include_facts` | only the receiver's scope | See Fact Scope Guard. |

## Steps

1. **Goal** in one sentence, in the person's own words if possible.
2. **Done:** what's finished, with links.
3. **Where things are:** file paths, docs, URLs, and IDs.
4. **Decisions:** what was decided, by whom, and why (one line each).
5. **Open:** questions waiting on the person, and blockers.
6. **Next step:** the single next action, specific enough to start right away.
7. **Check:** could the receiver continue with only this note? If not, add what's missing.

## Output format

```markdown
**HANDOFF → {receiver} · {date, time, zone}**
**Goal:** {one sentence}
**Done:** {items, with links}
**Where:** {paths, links}
**Decided:** {decision}, by {who}, because {why}
**Open:** {question}, waiting on {who}
**Next:** {one concrete action}
```

## Edge cases

- **The receiver is a person:** drop internal paths they can't open and use links instead.
- **The work is half-done:** say exactly where it stopped, for example "filled through page 3 of 5; nothing submitted".

## Boundaries

- Never include passwords, codes, or card numbers.
- A handoff passes information, not permission. Approvals still come from the person.