Illustrative workflow, not a live workspace result.
Repository state
Feature branch at the reviewed commit
Verified
Save request succeeds
Still untested
Reload after a new session
Next action
Test session recovery
Handoffs
The next agent starts where the last one stopped.
The objective, the repository state, the decisions already made and the work still unresolved travel together, so nobody has to reconstruct the conversation first.
Objective and constraints
Repository state
Decisions so far
Verified and still untested
Blockers and next action
Illustration of a handoff package. Your handoff carries your own project record.
Why use Handoffs?
A summary that says everything is done loses the distinction between a tested result and an assumption. Preserve that distinction when a task changes hands.
Keep the starting point precise
Include repository state and the next bounded action.
Preserve what was learned
Carry decisions, failed approaches, and constraints into the next session.
Challenge unsupported certainty
Keep missing evidence and stale references visible in the continuation record.
How Handoffs fits your work
01
Capture the current state
Supply the objective, repository reference, decisions, and evidence.
02
Validate the handoff
Review unsupported claims, missing information, and freshness.
03
Give the recipient a next step
Use the checked packet to continue within the stated constraints.
What to know before you start
A handoff is only as current as its references. The recipient must check for changes before relying on it.