household.devhandover

Introducing Handover

Looking complete isn’t being complete

The next agent only knows what your note says.

Gaps caught before the next agent inherits them.

A Handover note: its header, abridged

handoff: guest-checkouttrue_at_sha: a1b2c3d4e5f6first_action: Run the pending migration on the preview databaseverify_cmd: npm test -- guest-checkout && npm run typecheckstatus: done

A Handover is never done on belief, only on a passing check.

headervalid
Read the code
  1. Write Write a handoff from live git state.
  2. Score It scores the note against a strict format.
  3. Pick up The next agent picks up what is actually there.

Why we built it

An agent’s handoff note can look complete and still leave out what matters. The next agent inherits the gap and acts on it. Handover holds a note to a strict format: the commit its claims were true at, the one first action, and the command that proves the state. A note that says done must show how.

The result so far

A Handover note

Score100/100
Traps covered9 of 9
Valid

A session summary

Score8 to 16/100
Traps covered0 of 9
Valid

Three scenarios, three planted traps in each.

The paper

Paper · August 2, 2026 Handover: An Enforced Agent-to-Agent Handoff Document and a Trap-Based Benchmark for Measuring Context Transfer “A cold agent given only the artifact and repository access should reach the same decisions the sender would.” Read the paper

Install in Claude Code

/plugin marketplace add geekidharsh/handover/plugin install handover@handover

Two commands, then restart.

On GitHubRead the spec