handoff

Creating a handoff document transfers agent context by summarizing the current conversation, preserving key decisions, and referencing existing artifacts without duplicating them, ensuring the next session starts with complete continuity.

The best way to summarize a conversation for another agent is to create a portable handoff briefing that captures the discussion's current state, points to existing PRDs or diffs, and suggests follow-up skills for the next turn.

Yes, handoff documentation redacts sensitive information like keys, passwords, and personal data during the summarization process, ensuring the context transfer remains secure before being saved outside the workspace.

Yes, you can save a session continuity document outside your current workspace. The handoff process exports the portable briefing into the user's temporary directory for follow-up tasks.

You should use a context transfer document when a task needs to be paused or transferred. It references existing artifacts like PRDs, plans, issues, and diffs instead of duplicating them, preventing redundancy while maintaining context.

A key limitation is that adapting a handoff document requires you to explicitly state the next session's focus. The document only suggests follow-up skills and summarizes past context; it does not execute the next task automatically.