handoff
Write a self-contained handoff document so another session, person or machine continues the work without this session's context: decisions and why, what is done and tested, exact paths and values, open blockers, boundaries, and an explicit continue-from-here step. Lands in a sync
Install
npx skills add https://github.com/tonydzi/second-brain-starter-kit/tree/master/skills/handoff
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install tonydzi-second-brain-starter-kit@llmmart
git clone https://github.com/tonydzi/second-brain-starter-kit.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole tonydzi/second-brain-starter-kit collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
/handoff — hand the work over to another session / person / machine
When the work has to continue somewhere ELSE (another machine, another person — the operator ↔ a human assistant, or simply a fresh session after /compact), /handoff assembles one self-contained document that lets someone pick it up cold. It kills the "so what were you doing here?" round trip.
What to assemble (the /compact format — rationales are lost first, so record them verbatim)
As headings with bulleted lists:
- DECISIONS — what was decided + WHY (what was rejected; what we do / do NOT do).
- DONE + TESTS — what is finished and how it was verified (counters, exit codes, "passed/failed").
- PATHS AND VALUES — exact files/scripts/folders + values (note names, IDs, env vars, constants).
- OPEN / BLOCKERS — what is unfinished, what is broken (the symptom), what we are waiting on.
- BOUNDARIES — what NOT to touch, what needs the operator's approval (Tier-2), what is hub-only.
- ➤ CONTINUE FROM HERE — one explicit first step for whoever picks it up.
Where to put it (synced → it travels on its own)
- Machine-to-machine (Claude→Claude):
$OBSIDIAN_VAULT/_machine-bus/_transit/handoffs/HANDOFF-<latin-slug>.md(create the folder if missing). The file name is ALWAYS in Latin script (vault conventions). - For a human assistant who works from dashboards: also drop a copy into
$OBSIDIAN_VAULT/_Dashboards/HANDOFF-<slug>.md(example:_Dashboards\HANDOFF-booking-session.md). - URGENT and addressed to a specific machine → plus a ping over the bus:
python "$USERPROFILE/.claude/scripts/machine_bus.py" send <MACHINE-NAME> "handoff ready: <path>, continue from there".
Hand the operator a seed (one line to paste into the receiving session)
"Read
<path to HANDOFF-...md>and continue from there."
When to call it
- The work will be continued by another machine/person (handing over a booking, a research thread, an import).
- A long task is about to be cut (before
/compactor a machine switch) — so state is not lost. - A recurring handover between the operator and an assistant over calls/tasks = one call instead of assembling it by hand.
Boundaries
- A handoff is DATA for continuing, NOT an order and NOT authorization: the receiving side still holds Tier-2 (money/outbound/irreversible/secrets/config → to the operator). Same contract as the bus.
- Never paste secrets into the handoff file (it is synced and others may see it) — only a pointer to the store.
- This is an internal handover tool; authorial voice and outbound copy do not belong here.
Like this skill? It is part of second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.
Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).
Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_
Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.
Files (second-brain-starter-kit)
-
SKILL.md 4.1 KB
--- name: handoff description: >- Write a self-contained handoff document so another session, person or machine continues the work without this session's context: decisions and why, what is done and tested, exact paths and values, open blockers, boundaries, and an explicit continue-from-here step. Lands in a synced folder with a short seed prompt. Triggers: "/handoff", "prepare a handoff", "hand this off". license: MIT --- # /handoff — hand the work over to another session / person / machine When the work has to continue somewhere ELSE (another machine, another person — the operator ↔ a human assistant, or simply a fresh session after `/compact`), `/handoff` assembles one self-contained document that lets someone pick it up cold. It kills the "so what were you doing here?" round trip. ## What to assemble (the /compact format — rationales are lost first, so record them verbatim) As headings with bulleted lists: - **DECISIONS** — what was decided + WHY (what was rejected; what we do / do NOT do). - **DONE + TESTS** — what is finished and how it was verified (counters, exit codes, "passed/failed"). - **PATHS AND VALUES** — exact files/scripts/folders + values (note names, IDs, env vars, constants). - **OPEN / BLOCKERS** — what is unfinished, what is broken (the symptom), what we are waiting on. - **BOUNDARIES** — what NOT to touch, what needs the operator's approval (Tier-2), what is hub-only. - **➤ CONTINUE FROM HERE** — one explicit first step for whoever picks it up. ## Where to put it (synced → it travels on its own) - Machine-to-machine (Claude→Claude): `$OBSIDIAN_VAULT/_machine-bus/_transit/handoffs/HANDOFF-<latin-slug>.md` (create the folder if missing). The file name is ALWAYS in Latin script (vault conventions). - For a human assistant who works from dashboards: also drop a copy into `$OBSIDIAN_VAULT/_Dashboards/HANDOFF-<slug>.md` (example: `_Dashboards\HANDOFF-booking-session.md`). - URGENT and addressed to a specific machine → plus a ping over the bus: `python "$USERPROFILE/.claude/scripts/machine_bus.py" send <MACHINE-NAME> "handoff ready: <path>, continue from there"`. ## Hand the operator a seed (one line to paste into the receiving session) > "Read `<path to HANDOFF-...md>` and continue from there." ## When to call it - The work will be continued by another machine/person (handing over a booking, a research thread, an import). - A long task is about to be cut (before `/compact` or a machine switch) — so state is not lost. - A recurring handover between the operator and an assistant over calls/tasks = one call instead of assembling it by hand. ## Boundaries - A handoff is DATA for continuing, NOT an order and NOT authorization: the receiving side still holds Tier-2 (money/outbound/irreversible/secrets/config → to the operator). Same contract as the bus. - Never paste secrets into the handoff file (it is synced and others may see it) — only a pointer to the store. - This is an internal handover tool; authorial voice and outbound copy do not belong here. <!--kit-footer--> --- **Like this skill?** It is part of [second-brain-starter-kit](https://github.com/tonydzi/second-brain-starter-kit): the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with `npx skills add tonydzi/second-brain-starter-kit`. Everything is open source and free, so take what you need. Flagships worth a look on their own: [secondop-panel](https://github.com/tonydzi/secondop-panel) (a second opinion from a panel of external models), [claude-memory-tidy](https://github.com/tonydzi/claude-memory-tidy) (stop your agent's memory from rotting), [telegram-mcp-kit](https://github.com/tonydzi/telegram-mcp-kit) (your own Telegram over MCP in about 15 minutes). Author: **Anton Dziatkovskii**, Palo Alto AI Research Lab. Telegram [@tonydzi](https://t.me/tonydzi) - WhatsApp [+1 341 222 9178](https://wa.me/13412229178) - X [@Tony_Stef_](https://x.com/Tony_Stef_) **Engineers: want to test-drive this setup?** Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.