handover

Handover

One sentence the user pastes into a fresh session after /clear. The session that reads it knows nothing else, so the sentence carries everything needed to start.

The sentence

• What landed: the MR/PR and its number, what it did in a few words, the merge commit (short sha) and branch it is on.
• What is next: the issue or task by number and in a few words, plus any constraint the next session would otherwise get wrong (a rule from a review, a decision, an invariant).
• Where to start: the plan file to read first, by repo-relative path.

One sentence, however long; semicolons and an em dash are fine. Never start it with ! — the prompt reads a leading ! as bash mode, so a GitLab MR opens as MR !2376 (…), not !2376 (…). No greeting, no "you", no list. Names exact: numbers, shas, paths. Nothing the next session can find faster itself (the diff, the commit list).

Example: PR #146 (#130 notifications: the bell, the list and its desktop panel, seen per subject) merged as 5fd98a4 on main; next is #132 (reply notifications, the organisers' hourly email), which must keep notifications rows to ids and counts because the owner role reads them — read .claude/plans/130-notifications.md first.

Steps

1. Bring the plan file up to date first: it is what the next session reads.
2. Write the sentence, and nothing else, with the Write tool to ~/.claude/handover.md (overwrite it). The handover mod files it under ~/.claude/handovers/<session id>.md, one per session, so parallel sessions never overwrite each other. It shows a band above the prompt (/handover-copy copies it), and after /clear this session's sentence waits in the prompt (Tab takes it). A new terminal lists the repo's open sentences instead (the folder's, outside a repo); /handover N puts one in the prompt, and /handover drop N removes one. A sentence sent in a prompt, by Tab or pasted, leaves the list.
3. In chat, show it as a quote under "Handover for a new session:", and again in a fenced code block: the band and Tab live only in the terminal, and the block's copy button is how the web and phone clients take it. Then say in one line what is left to clean up (a local branch, a worktree) and ask before deleting any of it.

"Handover N" from the user

It is line N of the band, which you cannot see. The list is the mod's store (~/.claude/plugins/store/handover_*.json): the entries whose root is this session's place, newest first. A sentence's root is the git repo of the file the session wrote last (the plan file from step 1), else the folder the session started in; a session's place is the repo it started in, else that folder. Never answer it from ~/.claude/handovers/, which holds every repo's files and can lag the store. When one turns out to be done, say so and suggest /handover drop N.