handofflisted

Maintain the project's session-handoff so a brand-new session can pick up work cold - a file this skill writes directly (_meta/HANDOFF.md, HANDOFF.md, .claude/HANDOFF.md, or a per-project override), or an external tracker/board it signals via a freshness stamp when the project's handoff key is set to external mode. Use at session boundaries when the user says "wrap up", "update the handoff", "prepare to clear/compact", "write the handoff", or runs /handoff; use "/handoff init" to create the file in a project that lacks one (file mode only). Updates current state, in-flight work, decisions made and pending, and gotchas - or, in external mode, updates the external handoff and touches its stamp - the externalization pass that makes a session clearable.
hsb3/dotfiles-agents · ★ 0 · AI & Automation · score 70

Install: claude install-skill hsb3/dotfiles-agents

# Project Handoff Purpose: make every session **clearable** by externalizing all load-bearing state into one file a cold session can read in under ~10k tokens. The handoff is the bridge for NEW sessions (not resumes) - write for a reader with zero context. This skill is the **produce** edge of atelier's handoff loop; its enforcement partners are three co-homed hooks that read or gate on the SAME file it writes: `context-watermark`, `handoff-freshness-guard` (blocks a manual `/compact` when the handoff is missing or stale), and `session-handoff-surfacer` (surfaces the handoff to a fresh cold-start session). All three check the SAME candidate paths in the SAME order this skill writes to - keeping that list in sync is load-bearing, not cosmetic.  `context-watermark` nudges "run /handoff, then /clear or /compact" once context crosses the soft/hard watermark.  ## File location **Precedence contract - must match the hooks exactly.** The candidate list below is the same one, in the same order, that atelier's `handoff-freshness-guard` and `session-handoff-surfacer` hooks check: `_meta/HANDOFF.md` → `HANDOFF.md` → `.claude/HANDOFF.md`. Do not reorder or add a path here without changing the hooks' `CANDIDATE_PATHS` in lockstep - a mismatch means the hooks act on a different file than this skill writes. **Per-project override - file mode.** A project whose handoff lives somewhere else entirely (not one of the candidates above) can say s