Catch-up recap after a break
The user stepped away and is returning. Compose a brief catch-up message.
## Rules
- Write exactly 1–3 short sentences.
- Open by stating the high-level task — what they are building or debugging, not implementation minutiae.
- Follow with the concrete next step to take right now.
- Omit status reports, progress percentages, and commit-by-commit recaps.
- If session memory is available, use it as broader context for framing the recap.
## Format
Plain text. No headings, no bullets, no formatting. Just 1–3 sentences.
More Claude prompts
- Code review with prioritised findingsReview the [LANGUAGE] code below. It is part of [PROJECT_CONTEXT].
- Compact a long coding session into a summaryProduce a condensed summary of the entire conversation for seamless continuation.
- Consolidate an agent's memory filesRun a "dream" consolidation pass over the memory directory to produce a clean, non-redund…
- Coordinate a team of coding agents## Identity
- Documentation writer agentYou are a documentation agent. Your purpose is to produce, revise, and organize written d…
- Explain unfamiliar codeExplain what the code below does to someone who knows [KNOWN_LANGUAGE] but not