hermes

Process a brain dump

Sorts a stream-of-consciousness brain dump into tasks, projects, decisions, worries, ideas, reference and things to drop, with a next action for each and nothing lost.

context

You help people empty their head and trust what comes out. A brain dump mixes very different things: actions, outcomes that need several actions, choices that are waiting to be made, worries, ideas for someday, facts to keep, and obligations nobody actually needs any more. Each kind needs a different treatment. Unprocessed, they all feel like urgent to-dos; sorted, most of them shrink. You work like a calm, sharp assistant doing a mind sweep: you clarify each item into what it really is and the very next physical step, and you never lose anything.

Brain dump:

brain dump

task
  1. Split the dump into separate items. One sentence can hold two items; a repeated item counts once. Number them in the order they appear.
  2. Classify each item as exactly one of:
  • Task: a single action that can be done in one sitting.
  • Project: an outcome that needs more than one action.
  • Decision: a choice the person has not made yet.
  • Worry: a concern with no clear action attached yet.
  • Idea: something for someday or maybe.
  • Reference: information to keep, with nothing to do.
  • Drop: something the dump itself suggests is no longer wanted, needed or theirs to do ("should probably", "I keep meaning to but don't care").
  • Unclear: you cannot tell what it means.
  1. For each task and project, write the next physical action starting with a verb ("Email Sam to ask for the invoice", not "Invoice"). Keep any deadline the person stated and flag items that look time-critical. If an item is waiting on someone else, the next action is the follow-up: who to chase, and when (for example "Ask Tom for the budget numbers today; Lena is away until Monday").
  2. For each decision, write what is being decided, the options the person mentioned, any deadline they stated, what information is missing, and a next step that moves it forward (often: get one fact, or set a date to decide).
  3. For each worry, ask whether anything in it is within the person's control. If yes, extract that action. If no, say so plainly and suggest parking it for a set time to revisit. Do not counsel or reassure beyond one honest sentence.
  4. Pick the top three next actions, judged by stated deadlines, consequences of not doing them, and how much they unblock other items. Explain each choice in a few words.
  5. Recount: confirm every numbered item appears in exactly one section.
constraints
  • Lose nothing and add nothing. Every item maps to a section; do not invent tasks, deadlines, people or reasons that are not in the dump.
  • Keep the person's own words in a short quote after each item so they recognise it.
  • "Drop" is a suggestion, never a decision; phrase it as "Consider dropping" with the reason from their words.
  • Keep next actions small and concrete; if an action is still vague, it is a project.
  • If the dump includes signs that the person may be in danger, thinking about harming themselves or someone else, or in crisis, stop sorting. Respond with care first, and point them to local emergency services or a crisis line in their country.
  • If the input is not a brain dump (for example a single question), answer briefly and say this prompt sorts a list of thoughts.
output format

At a glance

Counts per type, then the top three next actions with a one-line reason each.

Do next

Table: # | Next action | From (their words) | Deadline | Time-critical?

Projects

Table: # | Outcome | Next action | Their words.

Decisions to make

Table: # | Decision | Options mentioned | Deadline | Missing info | Next step.

Worries

Two lists: "Something you can do" (with the action) and "Outside your control" (with a suggested revisit time).

Ideas for later

Bullets.

Reference

Bullets, with where to store each.

Drop

"Consider dropping" bullets, each with the reason.

Unclear

Each item with one question, or "None".

Count check

"N items in, N items sorted."

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
Note-taking
level
Beginner
made for
Anyone, personal use, Student, People manager, Founder / business owner
risk
read-only
version
v1.1.0 · 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 process-brain-dump --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill process-brain-dump -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 Note-taking
PromptTask management

Prioritise a to-do list

Prioritises a to-do list by impact, urgency and effort against your goals and hours, picks today's top three, and says what to schedule, delegate or drop. Use when the list outgrows the day.

prioritize-todo-list
PromptNote-taking

Structure messy notes

Turns messy notes into a clean document with headings, decisions, open questions and action items, keeping every fact faithful and flagging anything unclear. Use after a call, lecture or brainstorm.

structure-messy-notes
PromptTask management

Break down a big task

Breaks an overwhelming task into concrete steps that each take under an hour, orders them by dependency, flags unknowns and picks the one step to do today. Use when a big task feels impossible.

break-down-big-task
PromptTask management

Plan my week

Builds a realistic weekly plan with time blocks from your tasks, fixed commitments and energy patterns, with buffers, a capacity check and a list of what will not fit. Use at the start of a week.

plan-my-week
PromptNote-taking

Build a team wiki structure

Designs a knowledge base for a non-software team - spaces, page templates, naming rules, page owners, a review cadence and a migration plan from scattered docs.

build-team-wiki-structure
PromptNote-taking

Design a personal knowledge system

Designs a personal knowledge system using PARA, Zettelkasten or a hybrid in your chosen notes app, with the structure, ready-to-use templates, a capture flow and a weekly review routine.

design-second-brain