handofflisted

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".
tonydzi/second-brain-starter-kit · ★ 6 · AI & Automation · score 78

Install: claude install-skill tonydzi/second-brain-starter-kit

# /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`)