← ClaudeAtlas

handofflisted

Write a verified handoff file so work can continue in a fresh session, another repo or harness, or with a colleague; with `resume`, pick up from the latest one.
viettdann/arclight-kit · ★ 0 · AI & Automation · score 68
Install: claude install-skill viettdann/arclight-kit
# Handoff A handoff is a short, accurate Markdown file that lets a brand-new session pick up exactly where this one stopped. It lives in `${CLAUDE_PROJECT_DIR}/docs/` (written `docs/` below), is named with today's date and the task, and is written from verified facts. Accuracy is the whole point - a confident-but-wrong handoff is worse than useless. Invoked with `resume`, or as the first thing in a session with no work yet: go to Resuming. Otherwise write one. A handoff carries work somewhere this session can't follow: a later session after `/clear` or a restart, another repo or directory, another harness, a colleague, or a side task forked off without derailing this one. When the next step continues the same task in this session, `/compact <what the next phase needs>` keeps more of the reasoning. If the user invokes it in that case, write the handoff as asked and end the reply with that alternative ready to paste: `/compact <focus>` alone in a code block, the focus naming the next step, the files it touches, and the decisions it must keep. ## Writing a handoff ### Step 1 - Ground yourself in reality first Read the actual current state of the repo and any file you're about to describe; do not rely on your recollection of the chat (memory drift is exactly what compaction gets wrong). ```bash date +%F # today's date for the filename git status # staged / modified / untracked git diff HEAD --stat # which files changed (staged + unstag