checkpoint
Checkpoint
Pass the baton. Write a handoff document that summarises the current conversation well enough that a fresh agent can continue the work cold, with no access to this chat history.
Save it to a path produced by mktemp -t handoff-XXXXXX.md (read the file before you write to it).
What goes in it
- Where the work stands right now and what the next concrete step is
- The decisions already settled (so the next session does not re-open them)
- Anything currently stuck or uncertain
- Which Honest Loop skills the next session should use, if any
What stays out of it
Do not duplicate content that already lives in another artifact: PRDs, specs, plans, ADRs, issues, commits, diffs. Reference them by path or URL instead. The handoff points to the sources of truth, it does not copy them. A handoff that restates the whole spec is just a second spec that will drift out of sync.
If I passed an argument, treat it as the focus of the next session and tailor the document to that. A handoff aimed at "continue the build" looks different from one aimed at "review what was done".