handoff

Run /handoff with a note about what the next session is for. The skill writes a structured markdown doc to the OS temp dir and prints its absolute path, which you give to the next agent to read and continue from.

Handoff is for work that must travel to another harness, repo, colleague, or forked agent, buying portability. Use /compact when staying in the same session and only intent needs to survive, or /clear when nothing needs to survive.

Yes, harness swap is a primary use case. The handoff doc is a plain markdown file readable cold by any agent, so a new harness that cannot see the old context can pick up the work from the file.

The handoff doc is a transit document, not a project artifact, so it goes to the OS temp dir. Settled artifacts like specs, plans, and commits are referenced by path or URL only, since copies drift out of sync.

Unverified claims must be explicitly labelled as assumed and unverified. The next agent treats the doc as a contract and will not re-check, so beliefs written as fact become false premises for all downstream work.

Copy it to durable storage when the next session is more than an hour away or runs under a different harness, since temp directories die on reboot and some harnesses clear them between sessions. The same applies to any referenced files in temp.