← ClaudeAtlas

handofflisted

Generate a handoff document for the next session — prerequisites, session recap, next tasks
ledtorch/coding-agent-workflow · ★ 0 · Web & Frontend · score 70
Install: claude install-skill ledtorch/coding-agent-workflow
## Context Run these first and read the output — the last two are the **fingerprint** the next session verifies against, so capture them verbatim: ``` git branch --show-current git status --short # changed files this session git diff --stat HEAD git log --oneline -8 git log -1 --format=%h # HEAD at write time git diff HEAD | shasum # uncommitted-diff hash ``` ## Purpose The next session starts from zero context. This command produces a self-contained document that lets a fresh agent (a) read the right references first, (b) understand what just shipped, and (c) know what to do next — without scrolling this chat. ## Ground truth — the tree, not memory A handoff drifts two ways: claims written from conversation memory that no longer match the tree (compacted context, parallel sessions, late changes), and a tree that moves between write time and pickup. **At write time — verify every claim.** 1. The Context block above is captured fresh at invocation. Treat it, not conversation memory, as the truth about tree state. 2. Every file path, symbol, section anchor (`architecture.md §Content collection`), and count ("39 cases green") the draft names gets checked against the tree (Grep / Read / ls) **before the document is emitted**. A failed check is fixed or flagged — never emitted as remembered. 3. **Attribute the working tree.** `git status` shows everything — pre-existing and parallel-session files included. Cross-check file mtimes (`ls -laT <file