The prompt
Score 10 of 10, Excellent
Use it when You have a day of meetings and a pile of tasks, and want an hour-by-hour plan with a first action for each block and a fallback if the day slips.
- {{day}}
- {{working_hours}}
- {{meetings}}
- {{energy_and_breaks}}
- {{must_do}}
- {{tasks}}
Full prompt and why it works
Turn my tasks and meetings for {{day}} into a time-blocked schedule, so that I start the day knowing what I am doing in every hour and what gives way if the day goes wrong. Working hours: {{working_hours}} Meetings and fixed commitments, with times: {{meetings}} My energy through the day, and the breaks I need: {{energy_and_breaks}} The one thing that must get done today: {{must_do}} Tasks, with deadlines and how long I think each takes: """ {{tasks}} """ How to block the day: - Put the must-do task in the first focus block of the day, before email. - Keep focus blocks between 45 and 120 minutes, with hard thinking work in my high-energy hours. - Leave 10 minutes after each meeting for notes and follow-ups, and put email and messages into two set blocks rather than scattering them. - Include lunch and at least one other break. - Where I gave no estimate, make one and mark it with "~". Add a quarter to the estimate for anything I have not done before. - Stop at the end of my working hours. If the tasks do not fit, leave the extras off rather than shrinking blocks. Format: 1. The schedule: a table with the columns Time, Block, First action, Done when. The first action is the physical first step, such as "open the draft and write the summary paragraph". 2. If the day slips: which block to drop first and which second, and what must happen no matter what. 3. Did not fit: tasks left over, each with a suggested day. For example, a row in the right form: "9:00 to 10:30 | Focus: pricing proposal | Open last week's numbers and update the cost table | Section 2 drafted". That example shows the form only. Do not schedule anything over a meeting, and do not cut my estimates to make the day fit. A good schedule leaves me with nothing to decide once the day starts. If a task is too vague to block, such as "sort out the vendor thing", ask me what the next step is, or list it under Did not fit with that question.
Variables
- {{day}}
- The day you are planning, for example "tomorrow, Tuesday".
- {{working_hours}}
- When you start and stop, for example "8:00 to 4:30".
- {{meetings}}
- Each meeting or fixed commitment with its time, for example "10:00 to 10:30 team standup, 2:00 to 3:00 client call".
- {{energy_and_breaks}}
- When you are sharpest and what breaks you need, for example "best before noon, need a walk after lunch".
- {{must_do}}
- The one task that has to be finished today.
- {{tasks}}
- Everything else on your list for the day, with deadlines and estimates where you have them.
Why it works
- Format. Each block has a physical first action and a Done when, so starting a block takes no thought and you know when to stop.
- Length. Blocks stay between 45 and 120 minutes, with buffers after meetings and a hard stop, so the plan matches the hours you have.
- If unsure. A vague task gets a question about its next step instead of a block with nothing concrete in it.