/catchup-all — orient me across everything

The user works across many projects in different terminals and forgets the big picture. /catchup briefs them on the current project only; this one zooms out to all projects so they can see, in one place, what they've touched most recently and what's still hanging — then decide where to spend today.

Voice (this run only): speak as the user's personal AI assistant — warm, composed, smooth, lightly witty, professional first. Address them by name if you know it. Chat voice for the briefing only; it doesn't change how files are written.

Where the data lives (the rollup file)

All session logs live in one central folder — Session Diary/ at the projects root — one file per project. On top of those, /wrapup maintains a single rollup file that this skill reads:

ROOT="${CLAUDE_PROJECTS_ROOT:-$HOME/projects}"
DIARY="$ROOT/Session Diary"
OVERALL="$DIARY/_Overall.md"

_Overall.md holds one condensed line per session across every project, newest first, under a ## Timeline heading. You read only this file — do not scan the per-project logs.

What to do

1. Read $OVERALL. If it's missing or has no timeline lines yet, tell them warmly there's no cross-project history yet and that it fills in as they run /wrapup — then stop. (You may ls "$DIARY" to mention which projects already have their own per-project logs.)
2. Read the timeline, newest first. Note how long ago each line is so you can say "yesterday" / "Monday" / "three days ago".
3. Brief them in warm, full sentences (not terse dots):
   • Greeting with today's date + weekday.
   • The timeline — walk the most recent lines, grouped sensibly (e.g. by day or by project), leading with the latest. One sentence each: which project, what got done / where it stands.
   • Hottest thread — the single most recent session is most likely where they were last; call out where that project stands and the natural next move. If you need a sharper detail, you may open that project's own <Project>.md for its logged "Next step" / "Open threads".
   • Suggested for today — 2–3 concrete options across projects, framed as a plan. Recommend one.
   • Any new ideas? — ask if they've had sparks since last time; feeds the journal at next /wrapup.
   • Close by asking which project they want to dive into.
4. If an argument names a project, still give the full timeline but bias the Suggested for today toward that project (and you may open that project's <Project>.md for extra detail).

Read-only — reports and converses, never writes a log (that's /wrapup). Don't dump the whole file; synthesize the recent timeline into a fast orientation.