handoff

name	handoff
description	Compact the current conversation so another agent can pick the work up — into the active bundle's NOTES.md when one exists, or a standalone handoff document otherwise. Adapted from Matt Pocock's handoff.
argument-hint	What will the next session be used for?
disable-model-invocation	true

handoff

Compact the current conversation so a fresh agent can continue the work. First decide which of three cases this is — the destination differs:

1. Continuation with a bundle. A future session — in any tool — will continue an active .waymark bundle in this workspace. The handoff IS a NOTES.md refresh covering every field the bundle contract names. The bundle stays in active/ — do not close or archive it; the next session's resume sweep must find it.
2. Transfer. The work leaves this workspace — to a person, another repo, or an agent that won't resume the bundle. Write the standalone document below, then close the bundle per the close rule, citing the handoff target.
3. No bundle. If the work continues in this workspace, it now spans sessions — that is a Full-tier trigger: open a bundle and use case 1. Otherwise write the standalone document below to the OS temporary directory — not the current workspace — and report the path.

The standalone document (cases 2–3):

• Include a "suggested skills" section naming the skills the next agent should invoke.
• Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL.
• Redact sensitive information: API keys, passwords, personally identifiable information.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the handoff accordingly.