Recap

Reload the state of a project into a short, scannable brief so the user (or a fresh agent) can pick up where things left off. The point is synthesis — answer "where are we and what's next", not "list every commit".

What to gather

Pull from whatever the repo actually has; skip silently what it doesn't. In rough priority:

1. Git reality — current branch, divergence from origin/main (git log --oneline origin/main..HEAD), and working-tree status (staged/unstaged/untracked). This is ground truth for what's in flight right now.
2. Recent history — last ~10 commits (git log --oneline -10) to see the arc of recent work. Read the messages, don't just count them.
3. Intent docs — design/roadmap/planning files: DESIGN.md, ROADMAP*, README, TODO*, and anything under .context/ (Conductor's cross-agent scratch dir). These say what's meant to happen next; git says what already did.
4. Open PRs — if gh is available, gh pr list (and the current branch's PR if any) for review state and what's awaiting merge.

Run the independent reads in parallel. Don't read entire large files — pull the roadmap/next-steps sections and skim the rest.

What to produce

A tight brief, organized by these beats (drop any that are empty — don't pad):