← ClaudeAtlas

dw-handofflisted

Compact the live session into `.ai/work/<slug>/HANDOFF.md`: how far into the current task you are, what is applied but uncommitted, and which dead ends are already ruled out — so the next context window resumes mid-task instead of re-deriving it. Explicit-invoke only — you are the one who can see the session is about to end.
dominikwozniak/dw-solo-skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill dominikwozniak/dw-solo-skills
# dw-handoff — the middle of a task, saved `CHANGE.md` already survives a `/clear` at **task** granularity. This skill covers the gap that leaves — the middle of a task, where a checkbox cannot say which three approaches you already ruled out — and holds **only** that: decisions belong in `CHANGE.md`, traps in `## Gotchas`, follow-ups in the backlog. ## Output location `.ai/work/<slug>/HANDOFF.md`, beside the `CHANGE.md` it describes. `.ai/` is tracked in git. Find the change by branch, the same way the rest of the loop does: ``` grep -l "^branch: $(git rev-parse --abbrev-ref HEAD)$" .ai/work/*/CHANGE.md 2>/dev/null ``` - **One match** — write beside it. - **Several** — list them and ask. - **None** — **stop and write nothing.** A handoff needs a change to attach to; say so and point at `dw-shape`. An exploratory session with nothing shaped yet is what that skill is for. - **Detached HEAD** (the branch resolves to the literal `HEAD`) — say so, list every `CHANGE.md` under `.ai/work/` with its recorded `branch:`, and ask which one this belongs to. **One live handoff per change.** An existing `HANDOFF.md` is overwritten, never appended to — a second handoff describes a newer moment, and keeping both leaves the next session guessing which one is current. `dw-next` deletes it once it has ticked the task it described. ## Workflow ### 1. Name the task in flight Take the change from the grep above and, from its checklist, the task this handoff is about — usually the fi