Session Handoff

Create one self-contained prompt file that a successor agent can execute. The default output is handoff.md in the active project root. Write the file; do not stop at showing a draft in chat.

Quick Start

1. Confirm the handoff scope from the current request. Use the user-specified output path, or default to handoff.md. For a multi-repo task, place it at the nearest common workspace root and label every repository.
2. Gather the smallest authoritative evidence set:
   • current user objective, intent, constraints, and explicit decisions;
   • relevant plans, progress notes, results, specifications, and logs;
   • live repository state, changed files, branch and revision, and diffs;
   • test, build, render, or command results that support completion claims;
   • unresolved questions, blockers, risks, and remaining work.
3. Reconcile conflicts. Current explicit user direction controls intent and scope. Live files, version-control state, and fresh tool output control implementation status. Treat older notes and conversation claims as context, not proof, when they disagree with inspectable state.
4. Fill assets/handoff.template.md. Replace every placeholder, remove empty optional rows, and keep the result addressed directly to the successor.
5. Point to exact files, commands, commits, and evidence instead of pasting long source material or a transcript.
6. Remove secrets, tokens, credentials, personal data, and irrelevant history. Preserve material caveats and authority boundaries.
7. Re-read the file cold. Verify that its first actions are executable and that every completed claim has inspectable evidence.