Daily Planner
Daily Plan From an Overloaded List
Turn a messy task dump into a realistic day: one main outcome, time boxes, and what slips on purpose.
The Prompt
daily-plan-from-an-overloaded-list.md
You are a chief of staff. Plan a day I can finish. Date / hours available: {{hours}} Must happen today: {{musts}} Everything else on my mind: {{dump}} Meetings already booked: {{meetings}} Energy notes: {{energy}} Output: 1. The one outcome that makes today a success 2. A schedule with start - end times, including breaks and meetings 3. A "not today" list - parked with a when 4. A 3-item shutdown checklist for the last 15 minutes Rules: - Do not schedule more than {{hours}}. - Batch tiny tasks. - If {{musts}} cannot fit, say so and force a trade-off; do not hide it.
Negative prompt
Included when you copy the prompt
Do not schedule more work than {{hours}} allows. Do not hide an impossible {{musts}} list - force an explicit trade-off. Do not fill the day with tiny unbatched tasks or vague blocks like "catch up on email" without a time box. Do not invent meetings, deadlines, or energy constraints that are not in the input. Do not omit the "not today" list or the shutdown checklist. Do not motivational-speak; give clock times and parked dates.
Fill in your details below - this prompt updates as you type, then copy it.
Fill in your details
0 of 5 filled. Preview updates as you type - then copy the finished prompt (negative prompt included when present).
daily-plan-from-an-overloaded-list.md
Prompt preview
You are a chief of staff. Plan a day I can finish. Date / hours available: {{hours}} Must happen today: {{musts}} Everything else on my mind: {{dump}} Meetings already booked: {{meetings}} Energy notes: {{energy}} Output: 1. The one outcome that makes today a success 2. A schedule with start - end times, including breaks and meetings 3. A "not today" list - parked with a when 4. A 3-item shutdown checklist for the last 15 minutes Rules: - Do not schedule more than {{hours}}. - Batch tiny tasks. - If {{musts}} cannot fit, say so and force a trade-off; do not hide it.
Examples
Example input
Date / hours available: Thursday, 9:00 - 17:00 (7 hours real work after lunch; protect 12:30 - 13:00 lunch) Must happen today: Send investor update draft to co-founder by 16:00; prep 20-min demo script for Friday customer call. Everything else on my mind: - Reply to 14 Notion comments on pricing page - Review two candidate take-homes - Outline Q4 hiring plan - Fix broken Stripe webhook in staging - Book dentist - Clean up Linear backlog labels - Read competitor launch notes Meetings already booked: 10:00 - 10:30 standup; 14:00 - 14:45 1:1 with eng lead Energy notes: Deep work best before lunch; afternoons okay for admin and light writing.
What you should get
1. Success outcome Investor update draft in co-founder's hands by 16:00, with Friday demo script outlined enough to rehearse tomorrow morning. 2. Schedule (9:00 - 17:00) 9:00 - 9:15 - Scan inbox/Slack; park non-musts 9:15 - 10:00 - Demo script outline (talk track + 3 screens) 10:00 - 10:30 - Standup 10:30 - 10:40 - Break 10:40 - 12:20 - Investor update draft (numbers + narrative) 12:20 - 12:30 - Buffer / stretch 12:30 - 13:00 - Lunch 13:00 - 13:45 - Finish investor draft + send to co-founder 13:45 - 14:00 - Batch: book dentist + star Notion threads to defer 14:00 - 14:45 - 1:1 eng lead 14:45 - 15:30 - Batch admin: Notion comment replies (pricing only), Linear label tidy (30 min cap) 15:30 - 16:00 - Polish demo script; confirm Friday calendar 16:00 - 16:45 - Stripe webhook staging fix OR stop and document blocker 16:45 - 17:00 - Shutdown checklist Trade-off note: Candidate take-homes, Q4 hiring outline, and competitor notes do not fit; parked below. 3. Not today - Two take-home reviews - Friday 9:30 - 11:00 - Q4 hiring outline - Monday planning block - Competitor launch notes - weekend read / next Tue - Remaining Notion threads outside pricing - Friday admin hour 4. Shutdown (last 15 min) 1. Confirm investor draft sent and demo doc link in Friday event 2. Write tomorrow's top 3 in Linear 3. Close Slack; list any open Stripe webhook blocker in #eng
When to use this prompt
Use it when
- You need help with busy professionals.
- You need help with founders.
- You need help with students.
Skip it when
- You only need a one-line ask with no constraints, format, or context.
- You cannot supply the fill-in details the template asks for.
- A different category or tool-specific workflow fits the job better.
How to get a good result
Done when
1. Success outcome Investor update draft in co-founder's hands by 16:00, with Friday demo script outlined enough to rehearse tomorrow morning. 2. Schedule (9:00 - 17:00) 9:00 - 9:15 - Scan inbox/Slack; park non-musts 9:15 - 10:00 - Demo script outline (talk track + 3 screens) 10:00 - 10:30 - Standup 10:30 - 10:40 - Break 10:40 - 12:20 - Investor update draft (numbers + narrative) 12:20 - 12:30 - Buffer / stretch 12:30 - 13:00 - Lunch 13:00 - 13:45 - Finish investor draft + send to co-founder 13:45 - 14:00 - Batch: book dentist + star Notion threads to defer 14:00 - 14:45 - 1:1 eng lead 14:45 - 15:30 - Batch admin: Notion comment replies (pricing only), Linear label tidy (30 min cap) 15:30 - 16:00 - Polish demo script; confirm Friday calendar 16:00 - 16:45 - Stripe webhook staging fix OR stop and document blocker 16:45 - 17:00 - Shutdown checklist Trade-off note: Candidate take-homes, Q4 hiring outline, and competitor notes do not fit; parked below. 3. Not today - Two take-home reviews - Friday 9:30 - 11:00 - Q4 hiring outline - Monday planning block - Competitor launch notes - weekend read / next Tue - Remaining Notion threads outside pricing - Friday admin hour 4. Shutdown (last 15 min) 1. Confirm investor draft sent and demo doc link in Friday event 2. Write tomorrow's top 3 in Linear 3. Close Slack; list any open Stripe webhook blocker in #eng
Common mistakes
- Leaving hours, musts, dump vague - the model then invents placeholders.
- Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules.
- Stopping when the first draft appears instead of checking it against the success criteria below.
FAQ
- What do I fill in before I copy this prompt?
- Replace these placeholders with your details: hours, musts, dump, meetings, energy. Required fields are marked on the page. The prompt text updates as you type.
- Which AI tools is this prompt written for?
- It works best with ChatGPT, Claude, Gemini. Copy the filled prompt and paste it into the tool you already use.
- What should a good result look like?
- 1. Success outcome Investor update draft in co-founder's hands by 16:00, with Friday demo script outlined enough to rehearse tomorrow morning. 2. Schedule (9:00 - 17:00) 9:00 - 9:15 - Scan inbox/Slack; park non-musts 9:15 - 10:00 - Demo script outline (talk track + 3 screens) 10:00 - 10:30 - Standup 10:30 - 10:40 - Break 10:40 - 12:20 - Investor update draft (numbers + narrative) 12:20 - 12:30 - Buffer / stretch 12:30 - 13:00 - Lunch 13:00 - 13:45 - Finish investor draft + send to co-founder…
- What are common mistakes with this prompt?
- Leaving hours, musts, dump vague - the model then invents placeholders. Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules. Stopping when the first draft appears instead of checking it against the success criteria below.
Best for
- Busy professionals
- Founders
- Students
Related Prompts
More prompts like this — same topic and style.