A weekly planning prompt only works if you feed it the right inputs. “Help me plan my week” produces a generic list. The templates below ask for your actual constraints first, deadlines, energy levels, fixed commitments, so the plan that comes back is one you can actually follow.
Why Generic Planning Prompts Fail
A model asked to “help me prioritize my tasks” with no other input will default to generic advice: do the important thing first, batch similar tasks, and so on. None of that is wrong, but none of it is useful either, because it isn’t grounded in your actual week. The fix is the same one that works for every other kind of prompt: give it real inputs before asking for output.
Prompt: The Weekly Reset
“Here is my task list for the week, with rough time estimates and hard deadlines marked. Here are my fixed commitments (meetings, appointments) with their times. Build me a day-by-day schedule that respects the fixed commitments, front-loads anything with a deadline this week, and flags anything that won’t realistically fit so I can decide what to cut or delegate. Tasks: [list]. Fixed commitments: [list]”
Prompt: Prioritize by Impact, Not Urgency
“Here is my task list. For each task, estimate its impact on my top goal, [state your goal], on a scale of 1-5, separately from how urgent it feels. Then sort the list by impact first, urgency second, and tell me which top 3 tasks deserve my best hours this week regardless of how loud they feel right now. Tasks: [list]”
Prompt: The Friday Look-Back
“Here’s what I planned for this week and what I actually completed. Identify the pattern in what got pushed or skipped, was it consistently one type of task, one time of day, or one kind of interruption, and suggest one specific change to next week’s plan that addresses that pattern directly. Planned: [list]. Completed: [list]”
Making This a Weekly Habit
These three prompts work best as a loop: reset on Monday, prioritize whenever new tasks land mid-week, and look back every Friday. Over a few cycles, the look-back prompt starts surfacing patterns you wouldn’t catch on your own, like consistently underestimating one category of task.
Related Reading
Once your week is planned, our guide to task automation with meta-prompts shows how to hand off the recurring parts of the plan itself. For background on the impact-versus-urgency framework referenced above, see Wikipedia’s overview of time management principles.
Prompt: Turning a Task Dump Into an Eisenhower Matrix
A flat to-do list treats every task as equally important, which is exactly why urgent-but-trivial items crowd out the work that actually moves a goal forward. The Eisenhower Matrix — sorting tasks by urgency and importance — is easy to describe but tedious to build by hand every week, which makes it a good fit for a repeatable prompt.
Prompt: “Here is my raw task list for the week: [paste tasks]. Sort every item into one of four categories: Urgent & Important (do today), Important & Not Urgent (schedule this week), Urgent & Not Important (delegate or batch), Not Urgent & Not Important (cut or defer indefinitely). For each item, add a one-line reason for its placement. Then list the three items from ‘Important & Not Urgent’ that are most likely to get pushed out if I don’t schedule them now.”
That last instruction is the part most people skip when prompting for prioritization. Asking the model to flag what’s at risk of being deprioritized, not just what to do first, catches the slow-burning items — a skills course, a process fix, a difficult conversation — that never feel urgent enough to schedule until they become a real problem.
Prompt: Running a Five-Minute Weekly Retrospective
Planning the coming week without reviewing the one just finished means the same mistakes — overbooking Mondays, underestimating a recurring task — repeat indefinitely. A short retrospective prompt turns your calendar and task tracker into a feedback loop instead of a static schedule.
Prompt: “Here’s what I planned for this week and what I actually completed: [paste both lists]. Identify: (1) which planned tasks didn’t get done and any pattern in why, (2) which unplanned tasks consumed the most time, (3) one concrete adjustment to next week’s plan based on this gap. Keep the answer under 150 words — I want a quick read, not a full report.”
Capping the length matters. A retrospective prompt without a word limit tends to produce a long, diplomatic summary that just restates the input; forcing brevity pushes the model toward the one adjustment that’s actually worth making.
FAQ
Do I need to give the AI my whole calendar?
Just the fixed, non-negotiable blocks (meetings, appointments) and rough durations. More detail than that usually isn’t needed for a weekly plan.
How specific should my task list be?
Specific enough that a stranger reading it would know exactly what “done” looks like. Vague tasks like “work on project” produce vague scheduling; “draft section 2 of the proposal” produces a usable time block.
Should I re-run the planning prompt if my week changes?
Yes. Treat the plan as a draft, not a contract. Re-running the prompt with the updated task list takes seconds and keeps the plan honest.
