handover

Generate a handoff summary that captures the project overview, completed work, technical decisions, pending tasks, and next steps in a markdown file. The receiving agent reads this file to resume work with full context.

A handoff document should include the project overview, user requirements, completed and pending tasks, technical decisions with rationale, current state, known issues, warnings, and related files. Each item should be grounded in what actually happened in the session.

Require the summary to distinguish completed, attempted, and discussed work, quote the user's exact words for requirements, and mark uncertain details as needing confirmation. A self-verification checklist before saving catches fabricated claims.

Create one when ending a session, switching AI agents, or transferring work to a teammate. It is most valuable after long sessions involving multiple decisions, code changes, or unresolved tasks.

Summaries only capture what was explicitly stated in the conversation and may omit implicit context. They are high hallucination risk, so unverified claims should be marked as needing confirmation rather than stated as fact.