close-chatlisted

# /close-chat — Session closeout Run a structured closeout pass at the end of a Claude Code session so the persistent record (memory, deliverables, LORE, TODOS, git, tasks) reflects what just shipped, what's parked, and what's still open. Output is a short status report the user can scan before the chat is archived. ## When to use - Explicit invocation: `/close-chat` - User says (in order of strength): "close chat", "let's close out", "prepare to close", "wrap up", "session wrap", "end of session", "before I close" - After shipping a substantive artifact (PR opened, deploy landed, major doc finalized) — even without an explicit phrase, surface the closeout prompt - Do NOT auto-run for trivial sessions (single-question chats, doc-only commits, conversational exchanges) ## The nine-item checklist Walk through each item in order. For each: act if applicable, or explicitly say "skipped — not relevant this session." Silence on a step is not a pass. ### 1. Project memory If the session touched a tracked project (anything in `MEMORY.md` index), update the relevant `project_*.md`: - Current shipped state (PR links, commit SHAs, version) - Real data points if surfaced (e.g., concrete progress numbers like "3/3/7 complete" instead of stale "8 weeks") - Parked work (local branches, deferred follow-ups) - Key files index for fast orientation - Update or rename the file if the project's identity shifted (route renames, scope changes); also update `MEMORY.md` index entry If the se