← ClaudeAtlas

handofflisted

Session handoff — save comprehensive session state for cross-session continuity
x-mesh/xm · ★ 0 · AI & Automation · score 73
Install: claude install-skill x-mesh/xm
# x-handoff — Session Handoff (Save) Save comprehensive session state so the next session can pick up where you left off — including the **conversation narrative** that disk artifacts (git, decisions.json, traces) cannot capture. ## Model Routing This skill runs **entirely on the leader** (sonnet). It is NOT haiku-eligible, for two reasons: 1. Only the leader has the conversation history needed to compose the narrative (Step 1). 2. MCP tools like `mcp__mem-mesh__*` are frequently unavailable inside a dispatched Agent, and the mem-mesh mirror (Step 3) is an MCP call. A haiku sub-agent silently degrades the skill to file-only. Run the CLI with Bash directly from the leader. Do **not** delegate this skill to an Agent — the token saving is negligible and it breaks dual-write. **Guardrail**: never skip Step 1 to save tokens. Without the narrative, `/xm:handon` shows only "what was done," not "why we were doing it" — the next session has to re-derive the working direction from scratch. ## mem-mesh Backend (capability gate) **Do NOT decide by inspecting your toolset.** MCP tools are often *deferred* — listed by name with no loaded schema — so "is `mcp__mem-mesh__add` in my tools?" reads as "no" even when mem-mesh is fully available. That misread is what silently disabled dual-write. The gate decides **whether mem-mesh exists for this run** — nothing else. It is resolved BEFORE any `add` is attempted, and never revisited afterwards: 1. If `mcp__mem-mesh__add` is directly ca