wrap-sessionlisted

# Wrap Session Work gets lost to session limits, crashes, and "I can't remember where I put it" restarts. This skill makes every session end the same safe way. Run ALL steps — order matters (most fragile state first). ## Step 1 — Persist state to disk FIRST Before writing any summary, make sure everything built this session exists on disk. Unsaved artifacts, drafts, or analysis that only live in the conversation → write them to files now. ## Step 2 — Write the handoff note Create or update `HANDOFF.md` in the project's root folder: ```markdown # Handoff — <project> (<YYYY-MM-DD>) ## Where things stand <2-4 sentences: what got done this session, current state> ## Files that matter <absolute paths to every deliverable, template, and data source touched> ## Open items <unchecked boxes for anything unfinished, detailed enough that a fresh session needs no re-explaining> ## Decisions & rules established <conventions decided this session — naming, "never do X" — so they don't get re-litigated> ## Resume prompt <a single copy-paste prompt a brand-new session could run to continue exactly from here, including file paths> ``` ## Step 3 — File into the right place Route knowledge to the correct project folder or knowledge base. Update (don't duplicate) existing notes; link related people/orgs/projects. ## Step 4 — Deliverables visible For any shippable output (site, zip, doc, report): copy/zip the final deliverable to an easy-to-find location and reveal it in the file ma