← ClaudeAtlas

dev-handofflisted

Writes a structured summary document (HANDOFF.md) so work can be picked up again without losing context — covering what was done, what's still in progress, what's blocked, and what the next person needs to know. Use whenever a working session ends before a feature is complete.
talentedgeai/infinite-leverage · ★ 0 · AI & Automation · score 65
Install: claude install-skill talentedgeai/infinite-leverage
# Dev Handoff Session handoff protocol. Produces a HANDOFF.md so the next agent or developer can continue without losing context. ## Step 1 — Locate or Create the Change Folder Handoff files live at: ``` docs/engineering/changes/{YYYY-MM-DD}-{slug}/HANDOFF.md ``` Where `{slug}` is a short kebab-case label for the current feature or fix (e.g. `auth-refresh-fix`, `email-sequence-step3`). If the folder doesn't exist, create it. ## Step 2 — Write HANDOFF.md ```markdown # Handoff: {feature/fix name} **Date:** {YYYY-MM-DD} **From:** Developer agent **To:** {who is receiving — QA agent / next developer session / PM} **Branch:** {current git branch} ## What Was Done {2-5 bullet points of completed work} ## What Is In Progress {any work started but not finished} ## What Is Blocked {anything that cannot proceed without external input — name the blocker and who resolves it} ## Files Changed {list of modified/created files} ## How to Test {exact commands or steps to verify the work — not vague "run tests"} ## Context for Next Session {any non-obvious things the next person needs to know: - decisions made and why - things tried that didn't work - assumptions baked into the implementation} ## Open Questions {anything unresolved that the next person needs to decide or investigate} ## Spec Deviations _(optional — omit section if none)_ {List any deliberate deviations from `.specify/features/{slug}/spec.md`: - AC-N: {what the spec required} → {what was actually built}