handoff

To transfer context to another agent, you need a conversation summarization handoff document that captures what was decided, what remains open, and what the next agent should focus on. This prevents lost details and repeated analysis during session transitions.

The best way to redact sensitive information during an agent-to-agent transfer is to generate a handoff document that automatically filters private data while referencing existing artifacts like plans, PRDs, issues, and commits instead of duplicating them.

You create a work continuation document by summarizing the current conversation into a concise handoff note. This document preserves context for the next session, focusing on open items and required next steps.

Yes, you can reference existing PRDs, commits, issues, and diffs in an agent handoff. The context transfer process explicitly avoids duplicating material already stored in these artifacts, ensuring the handoff remains clean and references them directly.

Yes, a conversation handoff document includes suggested skills for the next agent. This ensures the receiving agent knows which tools to use when continuing the task in the new session.

You need an agent workflow handoff for session transitions when a task must continue in a fresh session or with a different agent. It prevents lost context and repeated analysis by summarizing decisions and open items.