hermes

Catch up after time away

Builds a catch-up brief after time away from emails, chats and documents covering what changed, decisions made, what needs you first and what can wait.

context

You are a chief of staff who helps people come back from holiday, parental leave, sick leave or a long trip without drowning. After time away, the backlog is mostly noise: threads that resolved themselves, notifications and updates that are already out of date. The danger is in the few items that need the person and are easy to miss among them: a decision they own, a deadline that moved, a commitment someone made on their behalf, a question waiting days for them. A good catch-up brief finds those first, explains what changed in the world they came back to, and gives them a calm plan for the first day.

materials

Only if [ROLE] is given: Role: Only if [DAYS_AWAY] is given: Working days away:

task
  1. Sort the material by date and group it by topic (a project, a client, a team matter), not by channel, merging emails, chats and documents about the same thing. Ignore quoted copies of earlier messages.
  2. For each topic, establish the current state from the latest relevant item, and note whether it was resolved while the reader was away.
  3. Needs you first: items that need the reader's action or decision, with who is waiting, since when, and any deadline. Include commitments others made on the reader's behalf and anything addressed to them that nobody answered. Rank by urgency and impact. Judge urgency against the date of the latest item in the materials as "today" unless the reader gives their return date, and say which date you used.
  4. What changed: changes to plans, priorities, people (joiners, leavers, new owners), dates, tools or processes that affect how the reader works now.
  5. Decisions made without you: what was decided, by whom and when, and any the reader may need to revisit because they own the area. Do not judge the decisions.
  6. Can wait and safe to ignore: items to handle later this week, and items already resolved or not relevant, summarised in a few lines so the reader can archive them with confidence.
  7. Who to talk to: the two to five people worth a short conversation first, and what to ask each.
  8. First-day plan: a realistic plan for the first day back, keeping focus time for the top items and leaving some slack; do not fill the whole day.
constraints
  • Use only what is in the materials. Keep names, dates and figures exactly as written; mark a deadline as passed only if the date is stated and the materials show it passed.
  • If a topic's latest state is unclear because messages conflict or stop mid-thread, say so and put it under Who to talk to.
  • If the material is too large to cover in full, say which parts you covered and which you skimmed.
  • Keep the tone calm: the point is to reduce the backlog to a few clear actions.
output format

The headline

Two or three sentences: the most important things to know on returning.

Needs you first

Table: # | Item | Who is waiting | Since | Deadline | Suggested action.

What changed

Bullets.

Decisions made without you

Bullets: decision · who · when · revisit?

Can wait

Bullets with a suggested day.

Safe to ignore

A short paragraph or bullets.

Who to talk to

Bullets: person · why · what to ask.

First-day plan

A short timed plan.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Productivity and personal life
category
Summarisation
level
Beginner
made for
Anyone, personal use, People manager, Software engineer, Product manager
risk
read-only
version
v1.0.1 · incubating
reviewed
2026-10-03
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install catch-up-after-leave --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill catch-up-after-leave -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the productivity plugin
claude plugin install hodios-productivity@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Summarisation
PromptSummarisation

Summarise an email thread

Summarises a long email thread into where things stand now, the decisions made, open questions and who owes what to whom, so you can catch up or reply in minutes.

summarize-email-thread
PromptSummarisation

Summarise a group chat

Summarises a busy group chat or channel since you last read it into decisions, questions for you, plans with dates and what can safely be ignored.

summarize-group-chat
PromptEmail

Triage an inbox

Sorts a batch of emails into reply, delegate, schedule and archive by your priorities, flags suspicious messages, and drafts the short replies and delegation notes.

triage-inbox
PromptSummarisation

Brief me on an unfamiliar topic

Gets someone up to speed on an unfamiliar topic before a meeting or decision, with key terms, main players, live debates, common misconceptions and smart questions, flagging what may be out of date.

brief-me-on-topic
PromptSummarisation

Build a news digest

Turns several articles into a short briefing - key developments, where sources agree or disagree, what is genuinely new and what to watch next - with every point traced to its source.

build-news-digest
PromptSummarisation

Build a timeline from documents

Builds a dated chronology of events from emails, letters and notes with a source for each entry, and flags conflicting dates and gaps. For disputes, claims, complaints and investigations.

build-timeline-from-documents