How to Turn a Brain Dump Into a One-Week Priority Stack

Anyone drowning in a messy note can turn a brain dump into a one-week priority stack in about 8 minutes: paste the dump, force rank / why / next-action fields, and ban inventing tasks you never wrote. Run it in ChatGPT, Claude, or Gemini—about one seven-day stack from one dump, zero productivity theater.

A one-week priority stack from a brain dump is an ordered list of at most seven commitments for the next seven days, each with a why and a next action, not a life roadmap and not a second brain manifesto. If the model invents a gym plan you never mentioned, you never did the job. Your nouns beat generic hustle.

This is not plan week from calendar dump. Calendar dumps start from timed events. This guide ranks free-form worries into a short stack. It is not turn messy note into one page brief. Briefs clarify a project. This guide sequences a week. It is not voice memo into dated task list. Voice memos become dated tasks. This guide forces priority order and a hard seven-day cap.

What you need

The raw brain dump text (paste exactly, typos included). Constraint nouns: week start day, hard deadlines already known, capacity line (light / normal / overloaded), max items (7), energy note if useful. ChatGPT, Claude, or Gemini. Eight minutes and one cold human pass against your real calendar.

Banned before you start: inventing goals not in the dump, OKR lectures, “build a system” essays, and stretching the week into a quarter plan.

Rank the dump into a seven-day stack

1. Paste the dump. Lock week bounds and max seven

Paste the full dump. Add short nouns: “Need: one-week priority stack. Max 7 items. Week of Mon 2026-09-08. Fields: Rank, Item, Why, Next action, Day hint. Do not invent tasks not in the dump.”

Instruct ChatGPT, Claude, or Gemini: “Rewrite this brain dump into a priority stack of at most seven items for the next seven days. Output a table: Rank (1–7), Item, Why (one factual sentence), Next action (verb + object), Day hint (Mon–Sun or flex). Do not invent tasks absent from the dump. Do not add habits I did not mention. Then stop.”

Good paste: “Overloaded week. Max 7. Deadlines only from dump.” Bad: “Make me a transformative quarter.” Quarter is out of scope.

2. Force Rank, Why, and Next action before fluff

Shape output so Rank 1 is the thing that breaks if ignored. Cap motivational padding at zero.

Instruct: “Sort by consequence this week, not by vibes. Ban ‘ fore’ and ‘optimize life.’ Prefer verbs: send, decide, book, draft, call, pay. Prefer Day hint only when the dump or a pasted deadline implies it. Then stop.”

Good: “1 — Submit invoice — Client pays Friday — Send PDF today — Tue.” Bad: “1 — Become more intentional about money energy.” Energy is not a next action.

Cap the stack at seven items

If the dump has twenty worries, park the rest under a single line “Parking lot (not this week)” with no fake ranks. Models love promoting everything to P1. Your job is a stack a human can finish, not a shrine to ambition.

3. Ban inventing tasks and productivity sermons

Tell the model: “If a task is not in the dump, do not add it. Do not invent workouts, journaling streaks, or inbox-zero rituals. Do not rewrite my job description. Keep Item nouns close to my words.”

ChatGPT will invent “block deep work.” Claude will add a gentle self-care row. Gemini will invent a stakeholder map. Cut all three gifts.

Hard fail: any row not grounded in the dump; any OKR framework dump; any “systems” lecture longer than the stack; any eighth ranked item sneaking in.

4. Tighten Next action to one verb phrase

Ask for Next actions a human can start in fifteen minutes. Ban multi-step epics.

Instruct: “Rewrite each Next action as eight words or fewer. One verb. One object. No ‘and then.’ No philosophy. Then stop.”

Good: “Email Sara the draft link.” Bad: “Begin aligning cross-functional stakeholders toward a shared narrative.” That is brochure strategy.

If Rank 1–3 still look identical in consequence, mark FAIL and rebuild: “Re-rank by what breaks this week. Keep max 7. Ban ties without a why.”

5. Cold calendar pass, then stop

Open your real calendar. If Rank 1 needs three hours you do not have, demote or split the Next action smaller. If a hard meeting already owns Thursday, move Day hints. Do not ask the model for a second life plan.

Check traps: invented habits, eighth items, vague next actions, quarter-scale goals. One pass. If the stack still lists “launch company rebrand” when the dump only said “fix homepage typo,” you never turned a brain dump into a one-week priority stack. Stop.

What good looks like

Trigger: Your notes app is a cloud of worries and the week already started.

Input: Brain dump text, week start, capacity line, max seven, ChatGPT/Claude/Gemini.

Output: Ranked stack ≤7, Why factual, Next action verb-first, Day hints honest, zero invented tasks.

Stop: After one cold calendar pass. No second-brain religion. No quarter plan.

Treat the stack like a short bridge from anxiety to action, not a personal operating system. Models love expanding “pay rent” into wealth mindsets. Delete expansions. Keep nouns you can check off. The calendar pass exists to catch fantasy time. Skip that check and you will “prioritize” a week that cannot exist.

Takeaways

- Paste the dump. Lock max seven and week bounds. Force Rank / Why / Next action.

- Ban inventing tasks not in the dump. Park overflow without fake ranks.

- Keep Next actions under eight words. Re-rank by what breaks this week.

- One cold calendar pass. Then stop building life OS inside the prompt.