← ClaudeAtlas

handoff-updatelisted

Update handoff.xml after a work session - preserve open state, detailed active recovery context, approved next work, planning state, and lasting project learnings
TomasLicek/ai · ★ 1 · AI & Automation · score 78
Install: claude install-skill TomasLicek/ai
<purpose> Update the project's `handoff.xml` (always in project root) at the end of a session or before stopping mid-task. Primary consumer is a **fresh session with zero prior context**. Write so the next agent can safely resume, choose the right next action, and avoid redoing work. </purpose> <core_policy> `handoff.xml` is not a work log, changelog, diary, or proof-of-work document. Keep only what is useful for future action: - unfinished active work that must be resumed or checked - approved next tasks that are ready to execute - human decisions needed before work can proceed - unresolved proposal/discussion state, preserved by leaving `<board>` alone - blocked work and why it is blocked - accepted backlog items, when the project wants them in this file - stable project facts, constraints, and landmines Delete completed items unless the fact is needed to prevent a future agent from redoing or misunderstanding open work. </core_policy> <active_exception> `<active>` is the intentional exception to "not a work log". When work is interrupted, compacted, or left half-finished, `<active>` MUST contain detailed recent-session recovery notes. Be as detailed as possible while staying relevant: what was attempted, what changed, what was touched, what was verified, what is suspected, what remains, and where the next agent should resume. This is the only place where "I did X, touched Y, was about to do Z" belongs. Once that task is completed, abandoned, or converted into a clean