handoff

A conversation summary for agent transition compacts the current session context into a handoff document. You need it when transferring an ongoing task to a new agent to ensure seamless continuity and avoid redundant explanations.

You create a handoff document by passing your transition planning goal to the Skill, which then compacts the conversation into a markdown file. This document references existing artifacts to avoid duplication and suggests focus areas for the next session.

Yes, creating temporary markdown files is required to generate and store the handoff document. The Skill uses these files to reference existing artifacts and structure the conversation documentation for the next agent.

Yes, the handoff document suggests skills and focus areas for the next session. By providing a directive like preparing for a follow-up meeting, the generated transition planning documentation targets those specific next steps.

The best way to avoid duplication is to reference existing artifacts within the generated handoff document. The Skill compacts the conversation summary while pointing the new agent to prior outputs, ensuring transition planning does not repeat previous work.

Agent transition planning requires referencing existing artifacts to prevent the new agent from recreating previous outputs. The handoff document uses these references to maintain conversation continuity and reduce the time required to document transitions.