| name | current-status |
| description | Catch the user up on the CURRENT state of this session's work — they were away and have not read anything you wrote. Give a concise status: what's done, what's in progress or waiting, anything that needs their input, and the next step. Use when the user says "/current-status", "current status", "status?", "where are we", "catch me up", "what's the state of things", "I was away — what happened". Session-scoped — for cross-project catch-up use /catch-up instead. |
current-status
The user stepped away and has not read any of your previous messages, files, or output. Bring them fully up to speed on the work in this session, assuming zero recall. Be concise and scannable — they want to know the state in seconds, not read an essay.
Do
-
Briefly glance at what's actually true now if relevant: the task list (TaskList), the last few things you did, any background job / scheduled task / pending decision. Don't re-derive — summarize what already happened.
-
Report the state in this shape (drop any section that's empty):
- ✅ Done — what's finished (1 line each, only the things that matter)
- 🔄 In progress / waiting — what's mid-flight, running in the background, or blocked on something
- ❓ Needs you — any decision, approval, or answer you're waiting on (state it as a clear question)
- ➡️ Next — the single immediate next step
-
End with one plain-language line: where things stand overall.
Don't
- Don't dump full file contents, logs, or long explanations — link/point instead.
- Don't re-do work or re-investigate; this is a readout of current state, not a fresh start.
- Don't pad. If everything's done and nothing's pending, say exactly that in a sentence.
