← ClaudeAtlas

wrap-session-uplisted

End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.
michaeljauk/brain-starter · ★ 5 · Data & Documents · score 75
Install: claude install-skill michaeljauk/brain-starter
# Wrap Session Up End-of-conversation review skill. Replays the current Claude Code session, identifies what was accomplished, what's still open, and documents everything in the right places before the context is lost. ## Trigger phrases - `/wrap-session-up` - "wrap up this session" - "anything left open?" - "let's wrap up" ## Step-by-step workflow ### 1. Replay the session Review the full conversation history. Extract: 1. **What was accomplished** — files created/edited, commands run, problems solved 2. **Open action items** — things discussed but not yet done, commitments made ("I'll do that later", "next step is..."), tasks the user mentioned wanting to do 3. **Decisions made** — technology choices, architecture decisions, approach changes 4. **New knowledge surfaced** — things learned about the project, codebase, or tools that should be persisted 5. **Files touched** — all files created or modified during the session 6. **Friction points** — anything that caused repeated correction, workarounds, or user frustration (skill misbehaved, tool returned wrong output, Claude misunderstood something repeatedly, a convention was unclear). Only log if it happened more than once or was explicitly called out. Run `git diff --stat` to get a concrete picture of what changed. ### 2. Check for loose ends For each open item identified, check if it was resolved later in the session or if it's genuinely still open. Common patterns: - User said "I'll handle X" → still open, needs