recaplisted

# Recap Explain a body of work to the person who owns it, in the terms they'd use. Two moments this is for: **mid-development**, when the thread of what's been done and why has gotten long, and **end of feature**, when reviewing the whole change before merging. This is not a changelog. `git log` already exists and is useless for this purpose. The job is to reconstruct *intent* — what was wanted, what that turned up, what it turned into — and state where things stand. Run this **inline** in the current session. No subagents: there's no judgment to keep independent here, and if this session did the work, its memory of the reasoning is the single best source for the "why". ## Scope - *(bare)* — current branch vs its merge-base with the default branch. - `<PR#>` — that PR vs its base (`gh pr view <n>`, `gh pr diff <n>`). - `staged` / `working` — uncommitted changes only. - `<ref>..<ref>` — an explicit commit range. - `since <date/ref>` — work since a point in time. Quote paths in shell commands — parens and spaces (e.g. route groups like `app/(main)/...`) break unquoted. ## Gather before writing Cheap, in rough priority order. Stop when you can explain the *why*, not just the *what*: 1. **This conversation**, if the work happened here — the strongest source for intent and for the causal chain between changes. 2. **Commits**: messages and order tell the story of how the work evolved (`git log --oneline`, `git diff --stat`). 3. **The PR description**, if one exists.