handoff-prompt

# Handoff prompt ## Contract | Field | Bound contract | |---|---| | Trigger | User says handoff <task>, write a handoff, delegate this, or wants a clipboard-ready prompt for another agent | | Authority | Write only the assembled prompt text and the local clipboard; no repository, VCS, credential, paid, published, or remote mutation | | Side effect | A standalone, path-free prompt is copied to the clipboard and the user gets a terse confirmation | | Done | Prompt is on the clipboard, contains no filesystem paths, no invented facts, and gives the receiving agent enough context to orient and decide whether to proceed | ## Inputs Required: the task the user names or clearly implies. Optional, gathered only to make the prompt useful: repo or product identity, relevant issue/PR/branch names or URLs, likely modules, constraints, known symptoms, and the desired output shape. Infer these from the current repo, recent discussion, branch name, linked issue/PR, docs, and obvious nearby context when the user gives only a short label. Do not perform the receiving agent's full independent review or decide its final technical direction. ## Procedure 1. Identify the task from the user text. When the user gives only a short label, infer the boundary from the current repo, recent discussion, branch name, linked issue/PR, docs, and obvious nearby context. Done when: the task is named in one sentence, and when inferred, the source of the inference (repo, branch, issue/PR, or discussion) is...