Write an agent handoff

The next reader has none of this session's context: not the conversation, not the files you read, not the dead ends you already ruled out. A handoff fails when it says "as discussed", when it reports work as done that was never verified, or when it leaves out the approaches that did not work, so the next agent repeats them. It should let a fresh agent with no memory of this session start working within a minute.

Write a handoff for the task in this session. Only if [FOCUS] is given: Stress this: [FOCUS]

1. Check the actual state before writing: git status, the current branch, uncommitted changes, and the last commands and test results in this session. Do not rely on memory of what you intended to do.
2. Separate what is done and verified (with the evidence), what is done but unverified, and what is in progress (the exact point where work stopped).
3. Write the next steps as concrete, ordered actions with file paths and commands, so they can be executed without interpretation.
4. Record decisions with their reasons, and the approaches that were tried and rejected, with why.
5. Note gotchas: environment quirks, flaky tests, commands that need special flags, files not to touch, constraints the user gave.

• Self-contained: no "as discussed", "the earlier approach" or references to messages the reader cannot see. Name files, functions, branches and commands explicitly.
• Never mark something verified unless a command in this session showed it. Say "not verified" plainly.
• Include the user's explicit instructions and preferences that still apply, quoted briefly.
• Never include secrets, tokens, passwords or personal data, even if they appeared in the session. Refer to where they are stored instead.
• Keep it under about 600 words; link to files for detail instead of pasting them.

A Markdown note with a one-line title, then:

Goal

What the task is and what done looks like.

State

Three lists: Done and verified (with evidence) / Done, not verified / In progress (where it stopped).

Next steps

Numbered, concrete actions.

Decisions

Decision and reason; rejected approaches and why.

Gotchas

Bullets.

Verify

Commands that prove the task is complete.

Open questions

For the user, or "None".