session-handover · git:20261108.4b37627 · 2026-11-08 · sha256 7d1d5e15a8f535c4

session-handover git:20261108.4b37627A

Immutable. This exact content never changes and is served at /api/v1/blob/7d1d5e15a8f535c4.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_cd3kqdczcic3pufa/7d1d5e15a8f535c452a03008026a0c10b4f87d5f69722b5b983a7cabea1e1cd7.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, and for picking up work from an earlier note. Use it when finishing a task, stopping part-way, handing work to someone else, or acting on a handover note, session note or earlier claim.
---

# 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 each claim it makes against the system of record, such as the database row or the live ticket, not other notes. Notes go out of date.

---

*Part of the Human-Approved Agent Playbook by DababonPro IT Solutions. Copyright (c) 2026 DababonPro IT Solutions. Licensed under the MIT licence; the full text is in the `LICENSE` file in this folder.*