compaction-handofflisted

# Compaction Handoff Protocol Context compaction is lossy. Create a deliberate checkpoint that lets the next session resume from verified state without replaying the full conversation. This protocol is **snapshot-based, not append-based**: - `MEMORY.md`: durable facts and pointers only. - `docs/decisions/`: durable, load-bearing decisions only. - `.handoff/CURRENT.md`: current resumable state; overwrite on every handoff. - Git and PR state: authoritative implementation snapshot. - `/compact` line: short pointer to the anchor, not another summary. > `strategic-compact` decides **when** to compact. This skill defines **how** to checkpoint. ## Goals A valid handoff is: - **Recoverable:** the next session can start from one exact action. - **Atomic:** the anchor refers to one coherent repository state. - **Evidence-based:** verified results are distinct from claims and pending work. - **Compact:** only load-bearing information survives. - **Idempotent:** rerunning updates existing state instead of duplicating it. - **Bounded:** state files remain within fixed size limits. ## Trigger Run on explicit compaction or handoff requests, or proactively before automatic compaction while there is still enough context to write a clean checkpoint. Do not run after compaction without first reconstructing the best available state. ## State and retention rules ### `.handoff/CURRENT.md` — transient resume SSOT - Single source of truth for current resumable state. - Overwrite; never