handoff

To transfer conversation context, you need a structured handoff document that summarizes goals, decisions, and open items. This approach condenses the current discussion into a markdown file, ensuring the next agent session maintains maximum continuity with minimal repetition.

The best way to summarize a multi-agent workflow is to generate a conversation summary tailored to the next session's focus. By providing a description of the upcoming work as an argument, the handoff document is shaped to address specific follow-on tasks and context persistence.

To create a handover document without duplicating existing artifacts, reference PRDs, plans, ADRs, or issues by their path or URL instead of repeating their content. This artifact-aware de-duplication ensures the handoff remains concise and directs the next agent to original sources.

Yes, you can tailor the agent handoff output by providing an argument describing what the next session should focus on. This argument is treated as a description of the upcoming work, shaping the generated handoff document to align with the specific task context.

The generated handoff markdown file is saved to a temporary file path created via the mktemp command. This operational instruction ensures the content is written to a secure temporary location where it can be read and reviewed before finalizing.

You need a context transfer document for agent collaboration when switching from one agent to another in a multi-agent workflow. It is required for task handovers and follow-on work where conversation context must persist across separate agent sessions to prevent losing valuable decisions.