handofflisted

# Create Handoff Preserve the live, resumable core of the work. Reference durable sources of truth instead of copying them. Read `references/evidence.md` when deciding what state must be externalized for a fresh task. Do not delegate handoff authorship: one owner must reconcile the current workspace, decisions, and verification into a single source of continuation truth. ## Respect the Handoff Contract - Create a handoff only on explicit request. - Do not continue implementation, make unrelated changes, or reopen settled decisions while preparing it. - Save the brief in the operating system's temporary directory by default so it does not become repository maintenance burden. - Save it in the workspace only when the user specifies a path or the repository has an established authorized handoff location. - Return the brief directly in the response instead of creating a file when the user requests response-only output. ## Reconstruct the Current Truth Verify the current state from available evidence rather than relying only on conversation memory: - active instructions, plan, specification, and accepted decisions; - workspace and version-control state; - changed and untracked files; - relevant command, test, build, and validation results; - open tool processes or runtime state; - external task, issue, PR, document, and deployment references. Distinguish completed work, partially completed work, proposed work, and unverified claims. ## Preserve What the Next Task Needs C