sup

---
name: sup
description: Catch the user up in one screen — what got done, what changed, what waits on them, what comes next. Use when the user asks "sup", "what's up", "where are we", "catch me up" or "status report", returns after a break, or a long stretch of work ends.
---

# Sup

> _Sup? Read the record, not your memory._

A **catch-up** answers four questions, plus the lessons engraved, for someone who just walked in. They read it once and know what to do. It covers the time since the user's last message, or since the point they name.

## Steps

1. **Read the record, not your memory.** Check the branch, the commits, open pull requests and the tickets the work touched, now, because other sessions change them. Look for a handoff too: the newest comment that opens with `**Handoff**` on this branch's open pull request or ticket, or the newest such note where the user's own agent instructions keep that project's notes. Name it, and check each of its lines before you report one: a handoff is a lead, not a fact. Done when each claim you will make has a fresh command behind it.
2. **Write the parts**, one line per item, with a short code on each so the user can answer by code:

   ```markdown
   **Done** — <what landed, with its proof: a merged PR, a passing check>
   **Changed** — <decisions made or reversed, and what they replaced>
   **Lessons** — <n> engraved: <snag>, <snag>
   **Waiting on you** — <questions and approvals, two options at most, recommendation first>
   **Next** — <the one next action>
   ```

   Read Lessons from the ledger engrave keeps for every repo: `bash ${CLAUDE_PLUGIN_ROOT}/scripts/lesson-ledger.sh since <that point in UTC, as 2026-10-31T12:00:00Z>`, one line per lesson, each with its snag and its home. With no lesson, leave Lessons out, and leave out any other empty part. Done when the whole thing fits on one screen.
3. **Add parked work.** When the user moved away from something unfinished, end with at most three lines: "Still want X?" Count only work they left, not work you found. Done when each parked item is asked once or dropped.
4. **Pick up a handoff.** When step 1 found a `**Handoff**` comment or note, run `do` on the work it names, after the catch-up is sent: the ticket or pull request it links is the source, so `do` step 0 asks nothing, and `do` resumes at the step that work's records show. Skip step 5 then: `do` ends in its own report. Done when `do` has started on the handed-off work, or no handoff was found.
5. **Look ahead.** Run `cerebro` as a forecast. Done when its proposals end the catch-up, or it found nothing to forecast.

Charter: C5 ([CHARTER.md](../../CHARTER.md)).