session-handover · git:20261102.7e43d29 · 2026-11-02 · sha256 1188f7097ca6366d

session-handover git:20261102.7e43d29A

Immutable. This exact content never changes and is served at /api/v1/blob/1188f7097ca6366d.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_cd3kqdczcic3pufa/1188f7097ca6366d382b67bd60df9c7843a31edeff910de6b8b4e5c2322e93dc.json

Then /plugin install session-handover@markdownregistry-cd3kqdczcic3pufa in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: session-handover
description: Procedure for ending a working session so the next person or agent can continue without guessing. Use it when finishing a task, stopping part-way, or handing work to someone else.
---

# Session handover

The next session knows only what was written down. Leave the facts it needs and nothing else.

## Record

One short line each, in the place your team keeps notes:

- What is now true
- What you verified, and how
- What is not done, or not verified
- Any blocker, and who it is waiting on
- The first next action

## Rules

- Write facts, not a transcript of files and commands. The history is already in version control.
- Use real dates, not "tomorrow" or "last week", because the note will outlive the session.
- Keep secrets and personal data out of notes.
- Mark anything unverified as unverified. The next session will trust what you write.
- Before acting on an old note, check the live system. Notes go out of date.