Claude, wrap it up.
How to end any Claude session with a decisions summary and handoff for the next chat.
Every session with Claude produces a lot of context that won’t automatically transfer to your files. Not Claude’s outputs but the decisions that were made, the topics that were covered and what you narrowed down that won’t be revisited. By the time you close the tab, the real grit of the work might be left completely off the record.
File state is recoverable, a git log is traceable, and a scheduled morning brief can surface what’s waiting. But none of that surfaces what was decided in the process unless you ask specifically, and even then Claude can miss key context. You don’t need to spend all that time searching past chats to find that one locked decision that Claude can’t seem to remember. The wrap prompt solves that.
Wrap It Up
Paste this directly into your Project instructions:
When I say “wrap”, summarize what we did, note any decisions, and give me three options for what to start with next time.
One word and the whole thing runs. That’s going to be enough for most sessions.
If you want the structured output with the exact fields, the handoff block, the session log — grab the full prompt at luckyd3v.com, save it as wrap.md, upload it to your Claude Project files, and change the instruction to:
When I say “wrap”, read wrap.md and run it.
Same trigger. More structure.
Does Claude automatically log session decisions?
No. Conversation history stays in the thread, but there’s no automatic log of what was decided, what was ruled out, or where the thinking landed. You can ask Claude to surface it after the fact. The wrap prompt captures it while it’s still present so you don’t have to go searching later.
What’s the difference between Claude Projects and a session log?
Claude Projects carry your setup, preferences, and working style forward across sessions. A session log captures what happened in a specific exchange, what was decided, what was dropped, what’s left open. Projects give Claude the stable context. A session log gives you the audit trail.
Can I automate session wrap-ups in Claude?
Yes. The quickest version is a Project instruction: when I say “wrap”, summarize what we did and give me three options for what to start with next time. One word trigger, the whole thing runs. Full structured version at luckyd3v.com/prompts/wrap.
This is one of the prompts baked into my upcoming Loopstack OS, a file-based operator system for running multiple projects with Claude.