/wrapup — checkpoint this session

A future session starts with zero memory of this conversation. Your job is to leave it a note good enough that /catchup can orient the user in ten seconds. They checkpoint every hour or so, so each run captures what's changed since work began this session.

Where the log lives (central Session Diary)

All session logs live in one central folder — Session Diary/ at the projects root — with one file per project, named after the project folder (e.g. Web App.md, Content Pipeline.md). This keeps every project's history in one browsable place. Resolve at run time:

ROOT="${CLAUDE_PROJECTS_ROOT:-$HOME/projects}"
DIARY="$ROOT/Session Diary"
mkdir -p "$DIARY"
# PROJECT = the top-level folder under $ROOT this session is in
CUR="$(pwd)"
case "$CUR" in
  "$ROOT"/*) REL="${CUR#$ROOT/}"; PROJECT="${REL%%/*}" ;;
  *)         PROJECT="$(basename "$CUR")" ;;
esac
LOG="$DIARY/$PROJECT.md"

$LOG is the file you read and write (e.g. Session Diary/Web App.md). If it doesn't exist, create it with the header below. Everything goes in the central diary — do not scatter logs into each project's .claude/ folder.

Alongside the per-project files there is one rollup file, $DIARY/_Overall.md, that aggregates a single condensed line per session across all projects. /catchup-all reads only this rollup. You write to it too (step 4 below), so it always stays in sync with the per-project logs.

What to do

1. Resolve $LOG as above and read it (create with the header if absent). Get today's date + weekday from context.
2. Write an entry from what actually happened — never invent. Concise dot points, not prose. Newest goes at the top, directly under ## Sessions.
3. If today already has an entry, append a #### HH:MM checkpoint block under it rather than overwriting — multiple checkpoints a day is normal.
4. Update the rollup — open $DIARY/_Overall.md (create it with the rollup header below if absent) and prepend one condensed line for this session under ## Timeline, newest first. Format: - **YYYY-MM-DD (Weekday)** · <Project> — <title>: <≤12-word what-happened / where-it-stands>. For a same-day checkpoint, add a fresh line rather than editing the earlier one — the rollup is an append-only timeline.
5. Confirm back in one warm line: the title you saved + the next step.

Entry shape

### YYYY-MM-DD (Weekday) — <2–5 word title you invent>

- **Worked on** — which project/idea; flag if it's a new idea or an old one being developed
- **Added / changed** — concrete things produced this session
- **Areas touched** — broad topics/files touched (not an exhaustive list); link key notes with [[wikilinks]] if this is an Obsidian-style vault
- **Decisions** — what got locked in, and why (brief)
- **Open threads** — unanswered questions / deferred items
- **Next step** — the single most useful thing to do next session
- **💭 Journal** — new ideas or sparks the user voiced (+ any /wrapup argument). "(none today)" if empty

The Journal line is the diary thread — it's how the user tracks where ideas come from over time, so capture the spark even if it's half-formed.

File header (only when creating the per-project file)

# Session Log — <Project>

Handoff + idea diary for the **<Project>** project. Newest on top. `/wrapup` writes; `/catchup` reads.

## Sessions

Rollup header (only when creating _Overall.md)

# Session Diary — Overall

One condensed line per session across every project, newest first. `/wrapup` appends; `/catchup-all` reads. Per-project detail lives in each project's own `<Project>.md`.

## Timeline

Keep entries skimmable — concise dots beat paragraphs, and never delete old entries; the log is the memory.