session-closelisted

Finalise a working chat for handover to a future session: reconcile what changed against verified state, update the project's canonical files each in its own lane, route this session's decisions to their durable homes, and emit a SLIM session-delta handover that points at those files instead of restating them. Use when the user says "close this chat", "wrap up", "finalise handover", "hand off", "we're done here", "/close", or "/handover-out" — and proactively when a chat is long or laggy and the user signals they'll continue elsewhere. The OUTGOING half of a session-continuity pair — see session-open for the receiving half. Reserve "catch up / get up to speed" for that skill.
Oldvictech/session-continuity · ★ 1 · AI & Automation · score 74

Install: claude install-skill Oldvictech/session-continuity

# Session Close Finalise from VERIFIED state, write each piece of state to its one home, hand off slim. The next session should inherit verified files and a one-page delta — not a conversation summary that may carry unverified claims. ## CONFIGURATION (adapt to your project) Two lanes of canonical files. Name yours: **Assistant-writable** (you draft; the user saves): - **ROADMAP.md** — the plan: sequence, status, gates, pending decisions - **TASKS.md** — actionable items only - **HANDOVER** — this session's delta (written fresh each close) - *(optional)* convention/process guides the project keeps **Externally-owned** (a second environment owns them; you can only request edits) — e.g. an agent's instruction file, a ledger of shipped work, anything living on another system's disk. If your project has none, skip Step 4 entirely. ## Operating principle One home per content type: the plan lives in the roadmap, actions in the task list, durable decisions in the project's decision home, per-work detail in its own artifacts. The handover holds ONLY the session delta plus pointers. If the handover is growing, content is sitting in the wrong home. ## Step 1 — Reconcile (the safeguard) List what changed this session that affects canonical state. Tag each item **VERIFIED** (confirmed against the most authoritative source available — disk, ledger, a real run) or **CLAIM** (asserted in conversation only). Never promote a CLAIM — a status flip, a hash, a "done", a metric the next