Use to get the user back up to speed mid-project — where we are, what was decided, what's next — so they don't lose the thread. Trigger when the user returns to a task, seems lost, or asks to be caught up or re-oriented.
Installs into .claude/skills of the current project.
Are you the author of Lets Catch Up?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ronbronstein-lets-catch-up)
---
name: lets-catch-up
description: Use to get the user back up to speed mid-project — where we are, what was decided, what's next — so they don't lose the thread. Trigger when the user returns to a task, seems lost, or asks to be caught up or re-oriented.
---
# Catch Up
Re-orient fast.
1. What's been done so far on this task/session.
2. Key decisions and the reasoning — check the decision log (My setup names it) if there is one.
3. What's still open or undecided.
4. The single best next step.
Keep it short and plain — brief the user, don't replay a transcript.
**Next move:** continue the work in progress, or `lets-start` to pick new work.
