I don't actually hate planning. I hate that my plans used to disintegrate by Tuesday afternoon, which made the whole Sunday ritual feel like writing a heartfelt letter to a stranger who would absolutely ignore it. So eventually I quit planning entirely, which — shocking nobody — made everything worse. My weeks became a reactive sequence of whatever email shouted loudest, and I'd end Friday genuinely unable to tell you what I'd accomplished.
The 10-minute Sunday setup
Now I have a standing 8pm Sunday block — short enough that I don't dread it, long enough to matter. I open the Plan My Week Around 3 Priorities (with a Ruthless 'Not This Week' List) prompt, paste everything out of Notion without editing a single line, and give Claude Opus 4.8 three priorities and my real daily hours. The word 'real' is doing enormous work in that sentence. I used to plan around the eight gloriously productive hours I imagine I have, not the five I actually manage to defend from meetings, Slack, and the human need to occasionally eat.
- Copy every task out of your tracker — do not pre-filter, that's the AI's job, not yours
- Enter honest working hours, not aspirational ones, or the OVERLOADED flag is meaningless
- Treat the 'Not this week' list as a decision you made, not a failure you suffered
Why a model beats my own optimism
Manual planning lets me cheat, and I always take the bribe. I keep one too many tasks because I'm a hopeless romantic about future-me's willpower. Claude, mercifully, is unsentimental: if a task maps to none of the three priorities, it goes to the deferred pile, full stop, no negotiation. That constraint is the entire point of the system. I tried this first with a faster, cheaper model and it was perfectly fine for the mechanical sorting — but Opus 4.8 is noticeably better at the judgment calls that make or break a plan. Which task to bump off an overloaded Thursday. What single thing to protect when the week inevitably compresses. Those are the decisions I'm bad at making in the moment, and they're exactly where a stronger model earns its keep.
The 'protect this one thing' line that changed everything
The single most valuable line of the output, for me, is the closing one: the one thing to protect this week. My old plans treated every task as roughly equal, which meant when the week got squeezed — and it always gets squeezed — I'd protect whatever happened to be in front of me at the moment of compression, usually the loudest thing rather than the most important one. Now Claude names the single non-negotiable up front, on Sunday, before any noise. So when Thursday goes sideways, I already know what I'm allowed to drop and what I'm not. That one sentence has saved more important work than the entire rest of the table combined.
What surprised me is how often the thing it tells me to protect is not the most urgent item but the most consequential one — the strategy doc that has no deadline and therefore always loses to things that do. Left to my own devices, I'll let a hundred small urgent tasks quietly eat the one important task with no due date, week after week, and then wonder why the big stuff never moves. The model doesn't fall for urgency theater. It protects what matters, and lets the urgent-but-trivial fight over the scraps.
The honest caveat
Here's the part the productivity-influencer version of this post would conveniently skip: the plan is only as good as the priorities you feed it. The first week I tried this, I gave it three vague priorities — 'make progress on the launch,' 'be more responsive,' 'do some strategy work' — and got back a vague, useless plan. Garbage in, beautifully-formatted garbage out. The fix was forcing myself to write priorities specific enough to be either done or not done by Friday. 'Ship the launch landing page copy' is a priority. 'Make progress on the launch' is a feeling wearing a priority's clothes. Once I tightened that up, the output got dramatically sharper, because the model finally had something it could actually map tasks against.
The mid-week re-run nobody mentions
The second habit that made this stick was re-running it mid-week when reality had clearly diverged from Sunday's plan. By Wednesday afternoon, after a couple of surprise meetings and one genuine emergency, my original table is usually half-fiction. Instead of white-knuckling the obsolete plan or abandoning the system entirely — my two historical failure modes — I just paste the remaining tasks and the two days left back in, with updated hours. Thirty seconds, fresh table, and the OVERLOADED flag catches the fact that I've now crammed Thursday and Friday with everything that slipped. A plan you're willing to regenerate is infinitely more durable than one you treat as sacred and then resent.
I used to think re-planning meant the first plan had failed. It doesn't. The first plan did its job — it told me what mattered and what to protect. The mid-week re-run just acknowledges that Tuesday happened, the way Tuesdays always do. Treating the plan as a living document instead of a Monday-morning contract is the difference between a system I've kept for six months and the dozen I abandoned by Wednesday in years past.
My weeks feel calmer now, and not because I do less — I do roughly the same amount. They feel calmer because everything I do is something I consciously decided mattered on Sunday, with a clear head, instead of something Tuesday-me panic-prioritized at 4pm with cortisol making the call. When the inevitable mid-week fire shows up, I have a document that tells me exactly what it's costing me, so I can choose to pay that cost on purpose. I pair this with my Daily Standup From Yesterday's Notes prompt to keep the daily execution honest against the weekly plan. Grab the Plan My Week Around 3 Priorities (with a Ruthless 'Not This Week' List) prompt on Prompt Dock, give it ten honest minutes this weekend, and let it hold the boundary you keep failing to hold for yourself.