ai-memory handoff

Use this skill for single-use cross-session handoffs. Handoffs are for the next agent, not durable project documentation.

Tools in this cluster

• memory_handoff_accept consumes the pending handoff when the user asks where we left off and no already-fetched handoff block is visible.
• memory_handoff_begin creates a terse next-session handoff only when the user is wrapping up, ending the session, or explicitly asks to save context for the next session.
• memory_handoff_cancel expires a mistaken pending handoff by exact handoff id.

Single-use handoff behavior

The SessionStart hook usually fetches and consumes any pending handoff before the agent sees its first prompt. If the current context already contains a pending handoff block, answer from that block directly. Do not call the accept tool again to find it in another project, because handoffs are single-use and the tool will normally return null after SessionStart consumed it.

If no pending handoff block is visible and the user asks where we left off, then use the accept tool with the client-aware project scope below.

Creating a handoff