Session Wrap-up

Project-Specific Instructions

If running in a project with a local CLAUDE.md or AGENTS.md, check for a "Session Wrap Up" heading. If found, follow those additional instructions alongside (and in addition to) the steps below. That section is also where the project declares its sessionlog directory — see sessionlog-template.md.

Restore Full Session History First

Reconstruct full history before anything else: context compaction hides earlier work, and without it the sessionlog will be incomplete.

1. For long or compacted sessions, delegate session-file analysis to a subagent (see subagent-tasks.md)
2. Follow the tool-specific restoration guide:
   • Claude Code: claude-code-session-restoration.md
   • Cursor: no restoration procedure yet. Use the current conversation and git log, and note "restoration limited (Cursor)" in the summary.
3. Combine restored history with current context before continuing

If restoration finds no prior work beyond current context, proceed — but log that restoration was attempted.

Parallel session safety: The user may have multiple sessions running. Filter by $CLAUDE_SESSION_ID and timestamp correlation. Never combine work from other sessions. If uncertain, ASK.

Session Type Detection

After restoring history, classify the session:

Session Wrap-up Checklist

1. Determine scope — everything between last /bye (or session start) and now. Verify each item was discussed in THIS conversation.
2. Assess work — files created, files modified, decisions made, research done, tasks completed, tasks remaining. Then refresh live state before calling anything open or done. The conversation's picture of PRs, builds, tickets and branches is a snapshot from when they were last looked at, and they keep moving while a session sits idle — a wrap-up once listed a PR as "awaiting review and merge" hours after it had been merged. For every item the summary or sessionlog will call pending, done or blocked, check its source now: the PR's state (gh pr view / bb pr view — before the first bb call, run bb --version | grep -q quatico-bb; on a miss, skip bb, mark the item unverified and name the installed bb and brew install quatico-solutions/tap/quatico-bb), the CI status of the latest commit, the ticket's status in the tracker, the branch after git fetch. Drop what is already done; mark what cannot be checked as unverified. Never carry a status forward from memory.

3. Sessionlog needed? Would anything important be lost if we clear this session now? Commits already capture what changed and when. A sessionlog is only worth creating for context not in the committed artifacts.

   Session produced...	Sessionlog?	Why
   Plan file only	Skip	Plan file captures everything
   Q&A only, no file changes	Skip	Nothing to preserve
   Code/doc changes with clear commits	Skip	Git history tells the story
   Feature with decisions, alternatives tried, non-obvious rationale	Create	Context not in the code
   Single file, but research/intent/sources behind it	Create	Log captures the why
   Plan execution with deviations or partial completion	Create	Plan-vs-reality delta is valuable

   Project rules override this table. A documentation or knowledge-layer repo may require a sessionlog for every session; if ## Session Wrap Up says so, follow it and skip nothing.

   If skipping, note **Sessionlog:** Skipped — [reason] in the final summary.

4. Sessionlog — find the directory per sessionlog-template.md. If no directory exists, skip this step entirely — do NOT create directories. If one exists, create or update the sessionlog per the template.
5. Update project status — if work relates to projects/*/, update its status.md.
6. Handle git — see git decision table below.
7. Print final summary — see template below.

Git Decision Table

Commit message: follow the project's commit convention (CLAUDE.md / AGENTS.md, or the commit-notation skill) when one is declared, and add Session wrap-up: YYYY-MM-DD as the last body line. Otherwise use [Brief description]\n\nSession wrap-up: YYYY-MM-DD.

Push if remote tracking exists.

Final Summary Template

## Session Complete

**Accomplished:**
- [item 1]
- [item 2]

**Committed:** [hash]
- [file list]

**Pending:**
- [ ] [task 1]

**Session:** Reconstructed from N compaction(s) · ~Xk input / ~Yk output tokens
           ↑ only include if compactions > 0; round tokens to nearest k

**Sessionlog:** `<sessionlog directory>/[file].md`

Ready to clear context.