catchuplisted

# catchup — back up to speed in one screen You stepped away from this chat for a while and the details have faded. The full conversation is still in context; you just need a fast re-orientation before continuing. catchup scans the transcript and hands back a tight brief: the thread, the current state, what's blocked on you, and the next moves. Nothing more. ## When it fires `/catchup`, or natural cues from a returning user: "where were we", "catch me up", "refresh me", "where are we", "remind me where we left off". ## Scope — read only this conversation Distill **only the current chat transcript**. Do **not** read git history, memory files, or project files to build the brief — days may have passed and the repo may have moved, but catchup reports what *we discussed*, not what the world now looks like. If the user wants the repo state too, that's a separate ask. Staying transcript-only keeps the brief honest about shared memory. If the conversation is short or barely started, say so in one line instead of padding a four-section brief out of nothing. ## The brief — always these four headers, in this order 1. **Thread** — one line: what we're working on. 2. **Where we are** — current state and the decisions already locked in. Pointers, not re-derivation: "we settled on X", not a re-explanation of X. 3. **Waiting on you** — open decisions or items pending *your* call. Always present: if nothing is blocked on the user, write "nothing — ball's in my court." 4. **Next*