name: assistant-handoff description: Continue a project in another assistant using a compact handoff tied to the current files and decisions. Use when a user wants to switch assistants or resume work without re-uploading context.
Assistant handoff
Turn a working project into a handoff another assistant can actually continue.
What to gather
Use the project space/folder or files the user supplied. Read the latest contents and note current version identifiers. If no project is identified, ask which one; do not sweep unrelated private spaces. Prefer an existing project brief, decisions log and work-in-progress file over a transcript dump.
Produce the handoff
Save one short Markdown document alongside the work, or update the existing handoff with a version check. Include:
- Goal and success condition: what the user is trying to finish.
- Current state: what works, what has been verified, and what remains uncertain.
- Canonical files: direct Stuff links/references, current versions and what each file contains. Never substitute a pasted copy for the authoritative reference.
- Decisions and constraints: accepted choices, important alternatives rejected, and any missing input.
- Next concrete action: the first useful step for the next assistant, including how to verify it.
Keep evidence separate from assumptions. Do not invent test results, approvals or tasks. A handoff is context, not permission to send messages, publish, spend money or change sharing.
Continue from a handoff
Read the referenced files again before editing: their current versions may differ from the handoff. Preserve newer work; on a version conflict re-read and reconcile instead of overwriting. Update the handoff after the task materially advances. End with the saved document link and a one-sentence prompt the user can give the next assistant.
Example: “Use this project handoff to continue the launch brief: [Stuff reference]. Read the current files first, then finish the next action.”