← ClaudeAtlas

handofflisted

Preserve a task across sessions or Coding Agents. Use when asked to hand off, save context, continue in a fresh session, switch a Fleet conversation between Claude and Codex, or pick up an existing handoff. Write a self-contained handoff or read it and continue; Fleet agent switching uses the existing fleet-handoff command and transfer controller.
verkyyi/claude-fleet · ★ 2 · AI & Automation · score 68
Install: claude install-skill verkyyi/claude-fleet
# Session handoff <!-- fleet skill --> Carries long-running work across a context-window boundary so a fresh session continues seamlessly. Two modes — **HAND-OFF** (write a doc) and **PICK-UP** (resume one). ### Fleet agent switches Inside Fleet, an explicit request to switch Coding Agent uses the existing `/fleet-handoff --to claude|codex` procedure in `commands/fleet-handoff.md` (or `~/.claude/fleet/commands/fleet-handoff.md`). This skill supplies the notes; the transfer controller owns exact source identity, transcript paths, target binding, drafts and loop ownership. Keep the notes private and outside the repo for that mode. On pickup, read the manifest and follow `previous_handoff` when original provenance is needed. A draft marked `unsent` is not an instruction to execute. An active Fleet loop already has a controller: use `fleet-loop.py status/defer/stop`, and do not create a second native `/loop` or timer. ### Decide the mode Explicit words always win: "hand off / save state / running low on context" → HAND-OFF; "pick up / resume / continue" → PICK-UP. Otherwise infer from the session, and **default to PICK-UP in a fresh session**: - **Fresh session** — you've done little/no substantial work yet this turn — **AND** a handoff doc exists → **PICK-UP** (resume the most recent one). This is the default at the start of a new session. - **Deep in a task** — lots already done this session, context filling up → **HAND-OFF** (write the doc). - **No handoff doc exists anyw