The task
It’s 8:47 AM. Inbox is 47 unread. Linear shows 18 open tickets assigned to you. Slack has 6 unread channels and your boss DM’d at 7 AM. You have a calendar that says 4 hours of focus blocks between meetings, and your honest assessment is you have 7 hours of actual work today before the day collapses. Your gut response is to start with whatever is loudest, which is how you got here. You want a stack-ranked list of what to actually do, what to defer with a date, and what to drop entirely, plus a specific plan for the first 60-minute block when your attention is still good.
Where AI helps — and where it does not
AI is good at applying a prioritization framework (impact × urgency, Eisenhower, RICE) consistently across a messy list, forcing a distribution instead of letting everything be “high priority,” and surfacing the dependencies you forgot about (the PR that unblocks two reviewers, the email that unblocks the legal call). It also handles the “drop” verdict better than most humans. Humans hesitate to drop; AI does it cleanly when told to.
What AI cannot do: know your office politics. It doesn’t know that your VP just got nervous about the launch, that your teammate is blocked on you specifically (not just “someone”), or that your skip-level is reading this week’s update. Feed those signals in as constraints. AI also cannot judge whether a task is “actually urgent” or “someone else’s urgent pretending to be yours”; challenge it on every urgency claim.
A specific failure mode: AI tends to mark too many things “do today” when the list is long. Tell it explicitly: “force a distribution. At most 3 do-today, 5 defer, the rest drop or delegate. If ‘do-today’ has more than 3, you’re not prioritizing.”
What to feed the AI
- Full task list, pasted from anywhere (Linear, Asana, Notion, inbox subject lines, Slack threads; messy formatting is fine)
- Real hours available today after meetings (be honest, “7 hours” is rarely true)
- Hard constraints: things you cannot drop (committed deadlines, people waiting on you specifically, calendar holds you can’t move)
- Office context: what your manager will notice if you skip, what your team is blocked on
- The one task you’ve been avoiding (every list has one); name it so the model can decide whether avoidance is the right call
- Your energy level honestly. High-energy 60-min blocks should go to cognitive work; low-energy time goes to admin
- The single “if today fails, why” item: what failure would make tomorrow much worse
- A separate “personal” list if you’re combining work and life; the framework still works
Copy-ready prompt
Stack-rank my task list for the next {hours} hours.
Full list (paste — messy is fine): {paste}
Hard constraints (cannot drop): {paste}
Office context — who is blocked on me, what manager will notice: {paste}
The task I've been avoiding: {paste}
The "if today fails, why" item: {paste}
My energy distribution: {paste — "good 9-11, ok 1-3, drained 3-5"}
Framework: impact × urgency.
For each task, return:
- Rank (1, 2, 3...).
- Verdict: do-today / defer-with-date / drop / delegate-to-whom.
- One-line rationale citing impact AND urgency separately ("blocks 2 reviewers + needed for end-of-day calibration").
- A flag if this task unblocks others ([UNBLOCKS: list]).
- An estimated minutes (be realistic — most tasks take longer than expected).
Rules:
- Force a distribution: at most 3 do-today items, at least 5 defer-with-date, the rest drop or delegate. If you have more than 3 do-today, you are not prioritizing.
- Every defer needs a specific date. "Later" is not a date.
- Drop is a real verdict. Use it. About 30% of inbox items deserve drop.
- For do-today items, sequence them by both dependency (unblockers first) and energy (cognitive work in high-energy hour).
End with a 60-minute morning-block plan:
- The single task to start with at {time}.
- Why this task, not the noisy one.
- What success looks like at the 60-min mark.
- What to do if the task is bigger than 60 min (stop and re-plan, don't push through).Shorter variant — daily 5-min standup
Yesterday I did: {list}. Today I have {hours} hours. Inbox highlights: {paste}. Pick the 3 do-today items. Defer everything else with a specific date. No "later." Lead with the unblocker.Sample output
A useful stack-rank row: “1. Ship the migration PR — do today, ~90 min — blocks 2 reviewers and required for end-of-day calibration meeting. [UNBLOCKS: design QA, data validation].”
A useful “defer-with-date” entry: “Refactor old config file — defer to Nov 24 (Friday focus block) — high effort (~3 hours), no current blocker, but worth doing before Q1 planning. Calendar-block it.”
A useful “drop” entry: “Reply to recruiter email — drop — you have a job you like and this recruiter has emailed 3x in 6 months without a real role. Mark as read, don’t reply. If they email a 4th time with a specific JD, reconsider.”
A useful 60-min morning-block: “9:00-10:00 — open the migration PR file in your editor and finish the diff. Do not open Slack first; the unblocking value is higher than anything you’ll see in Slack. Success at 10 AM: PR is committed and review-requested. If the diff is bigger than expected, stop at 10 AM, post a ‘I’ll have this by 2 PM’ update in the channel, and come back after lunch — don’t push through and lose the next 2 hours.”
A useful avoidance-call: “The task you’ve been avoiding is the contract review with Legal. Verdict: do-today at 10 AM. Avoidance has cost you 4 days already, and Legal closes at 5 PM Fridays — if you push it again, the deal slips a week. 30 minutes.”
How to refine
- Force the distribution: “Re-check: at most 3 do-today, at least 5 defer-with-date. If do-today has 4+ items, the 4th becomes a defer with a date. The constraint matters more than my objection that everything is urgent.”
- Defer needs a date: “Re-read defer entries. Every defer must have a specific date — ‘next week’ is not a date; ‘Nov 24’ is. If the date isn’t specific, the item goes back to ‘drop’ or ‘do today.’”
- Use drop liberally: “Re-read the drop section. About 30% of inbox tasks should drop; if you have <20%, you are too cautious. Drop is a verdict, not a failure. Common drop candidates: 6+ month-old emails, FYI Slack threads, recruiter outreach without specific JD.”
- Surface dependencies: “Re-tag every task with [UNBLOCKS: list] if it unblocks others. Tasks that unblock others jump to the top of do-today, regardless of personal interest.”
- Anchor the morning block: “Re-check the 60-min plan. The first task must be high-impact and cognitive, not admin. If it’s an email or a meeting prep, move to a later block; morning energy is your scarcest resource.”
Common mistakes
- Padding the do-today list with easy items to feel productive: finishing 5 easy tasks beats finishing 0, but finishing 1 hard task beats finishing 5 easy ones; force the distribution
- Defer = a black hole: without a specific re-look date, deferred tasks live forever in your guilt pile; every defer gets a calendar entry
- Letting the model treat all “urgent” tasks as equal. Challenge each one; “my boss said this is urgent” is data, “I feel like this is urgent” usually isn’t
- No dependency flags. The PR that unblocks two reviewers is worth more than 5 self-contained tasks; tag unblockers explicitly
- Skipping the avoidance task. Every list has one; the model should call it out and decide whether avoidance is the right call (sometimes it is, when the task is genuinely lower priority, but usually it isn’t)
- Putting cognitive work in low-energy slots. The 3 PM crash is not when you should write a strategy doc; do admin then, write in the morning
- Running this once a week and never updating. The list goes stale; daily during sprint weeks, weekly otherwise, with a 5-min re-rank at any major shift (new urgent ask, day blown up)
- Treating it as an assistant who decides. The AI proposes; you commit. The decision still requires your office context and your honest energy assessment
FAQ
- Does this work for personal tasks too?: Yes. The framework holds: swap “blocks 2 reviewers” for “kid pickup,” “manager will notice” for “partner has been asking.” Combine work and life lists if your day blends them; force the distribution across the combined set.
- How often should I run this?: Daily during sprint weeks or any week where your task list is shifting hourly. Weekly otherwise. Less than weekly and the list goes stale: defer dates lapse, drop candidates pile up, and the framework loses its bite.
- What if my manager keeps adding new “urgent” items?: Two moves. First, when they add an item, ask “what should this displace?”. The answer reveals true urgency. Second, run the prioritization in front of them once; seeing the 3 do-today + 5 defer + rest dropped is what builds shared trust on capacity.
- The model is too conservative on drop. What changes?: Add: “About 30% of an inbox-style list deserves drop. If your drop count is less than 25% of the list, you are too cautious. Drop is a verdict, not a failure mode. Common drop candidates: 6+ month-old emails, FYI Slack threads, vague ‘when you have time’ asks.”
- What about tasks I should delegate but don’t know to whom?: Tag them “delegate-TBD” and add “decide owner this week” to the do-today list. Unowned delegation is just deferred personal work; assigning ownership is itself a do-today.
Related
- AI weekly planning
- AI feature prioritization
- Workload Prioritization Prompts: 12 Templates to Decide What Not to Do
- AI Drafts Your Project Status Update
- AI Habit Tracker
Tags: #AI writing #Office #Workflow #Task priority #Planning