A weekly plan becomes useful when it shows what fits, what does not and which assumptions could change the answer. This prompt turns competing tasks into a proposed schedule with a visible capacity calculation. It does not create commitments or calendar events. Its purpose is to support a planning decision without disguising overload as a neatly formatted list.
Establish the available time before ranking tasks
Begin with working windows rather than a nominal number of hours. A person available from 09:00 to 12:00 has a different scheduling problem from someone with the same total time scattered across short gaps. Supply the timezone and, when relevant, the actual dates of the planning week.
Subtract fixed commitments that fall inside those windows. Do not subtract a meeting outside the supplied working hours unless it genuinely reduces the time available for these tasks. Check for overlapping commitments before calculating the remaining capacity.
Then reserve the requested buffer from the remaining flexible time. This template defines percentage buffer against that net time unless the preferences specify another basis. Showing the basis matters: the same percentage applied before or after meetings produces different numbers.
Keep three totals visible: fixed commitments, scheduled task effort and reserved buffer. Unallocated time can remain separate. A schedule need not consume every remaining minute to be a coherent proposal.
Prepare the five inputs without hiding uncertainty
Use availability for working windows and timezone. Use commitments for immovable events and their durations. If a commitment is tentative, label it so the output can distinguish a fixed restriction from a planning assumption.
Use objectives to state the outcomes that matter this week. “Make progress” gives less direction than “submit the report draft and unblock the billing review.” Use tasks for estimated effort, deadlines, dependencies and any minimum useful deliverable. Distinguish a deadline someone has confirmed from a preferred completion date.
Use preferences for buffer, focus periods, splitting rules and the priority rule to apply when everything cannot fit. State whether tasks may be divided across days and whether a meeting requires preparation or recovery time.
Replace missing values with “not supplied” rather than manufacturing precision. A task without an estimate can remain unscheduled pending an estimate. If the model proposes a placeholder duration, require it to label that duration as an assumption and exclude any claim that the estimate is confirmed.
Rank outcomes and expose the tradeoff
Priority is a decision rule, not merely a sorted list of deadlines. A task due later may need an early start because it depends on another person’s feedback. A smaller task may unblock someone else. Ask the prompt to explain its ordering using the supplied objectives, deadlines and dependency relationships.
When capacity is insufficient, distinguish deferral from scope reduction. Deferring a four-hour cleanup leaves the work intact for another period. Replacing a full report with a shorter draft changes the deliverable and needs an explicit decision. Neither should be hidden inside an optimistic time estimate.
Write the rejected alternative alongside a material choice. For example, preserving the report deadline may mean leaving part of dashboard cleanup unscheduled. That explanation helps the user assess the proposal rather than treating the generated ranking as authority.
For teams designing a repeatable planning process, choose a workflow before an autonomous agent offers a related place to consider responsibility and review.
Work through a fictional week
Consider a fictional operations analyst named Mina. Her availability is Monday through Friday, 09:00–12:00 in Asia/Karachi. Her commitments are a Tuesday meeting from 10:00–11:00 and a Thursday meeting from 09:00–10:00. Her objectives are to finish a report and unblock a billing fix.
Her tasks contain four hours of report drafting, a separate one-hour stakeholder review, one hour of final edits, two hours of billing review due Tuesday and four hours of dashboard cleanup without a deadline. Drafting must finish before the stakeholder review, which must precede final edits. The report is due Friday. Her preferences request a 20 percent buffer and focus blocks of up to 90 minutes, with shorter blocks permitted around meetings.
The week contains 15 hours of working windows. Subtracting two meeting hours leaves 13 flexible hours. Reserving 20 percent of those hours leaves a 2.6-hour buffer and a task capacity ceiling of 10.4 hours.
The report work, stakeholder review and billing review total eight hours. All requested work totals 12 hours, so it cannot fit within the task ceiling. The plan must defer some cleanup or propose an explicit change elsewhere. It should not quietly remove the buffer to make the arithmetic appear complete.
Build a schedule that respects sequence and windows
A possible fictional Monday allocates 90 minutes to drafting, 30 minutes to billing review and one hour to buffer. Tuesday allocates billing review from 09:00–10:00 and 11:00–11:30 around the fixed meeting, then another 30 minutes to drafting. Billing review is now complete, and drafting has used two hours.
Wednesday allocates two hours to the remaining draft and one hour to stakeholder review. That review placement is conditional on the stakeholder’s availability; the proposal must flag it for confirmation. Thursday preserves the meeting, schedules one hour of final edits, then assigns 30 minutes to cleanup and 30 minutes to buffer.
Friday assigns 90 minutes to cleanup, 66 minutes to buffer and leaves 24 minutes unallocated. Across the week, scheduled tasks total ten hours, buffer totals 2.6 hours and the unallocated allowance totals 0.4 hours. With meetings, the schedule accounts for all 15 hours.
Two cleanup hours remain deferred. The shorter billing blocks are a visible consequence of Tuesday’s meeting, not an unnoticed violation of a mandatory 90-minute minimum.
Handle feedback delays and estimation changes
The fictional schedule depends on Wednesday’s review occurring before Thursday’s edits. If that availability is unknown, the model should identify a provisional slot and a question for Mina. It should not claim the stakeholder has agreed to attend.
Add one replanning checkpoint, such as Wednesday after the proposed review. At that point, compare remaining effort with remaining capacity. If drafting took longer than estimated, update the remaining estimate instead of pretending the original plan is still feasible.
Keep waiting time distinct from personal work time. A report awaiting feedback may be blocked without consuming every hour until the response arrives. Conversely, a one-hour live review occupies an actual working window and must be counted.
If feedback arrives too late, present the resulting choice: move final edits, reduce the deliverable with approval or revise the deadline. Do not invent a promise that another person will respond in time to preserve the schedule.
Stress-test a week with 25 percent less capacity
Define the reduction before calculating it. In this template, the fallback reduces net flexible capacity by 25 percent while leaving fixed commitments unchanged, unless the input specifies a different scenario. For Mina, 13 flexible hours become 9.75 hours. A 20 percent buffer then uses 1.95 hours, leaving 7.8 hours for tasks.
The eight-hour report-and-billing package no longer fits, even after every cleanup hour is deferred. The gap is 0.2 hours, or 12 minutes. Reporting that small deficit is preferable to silently treating estimates as adjustable facts.
One possible scope proposal is a shorter report draft estimated at half an hour less work, making the package 7.5 hours. That is a different deliverable requiring approval, not evidence that the original work became faster. If scope cannot change, the fallback remains infeasible under the supplied assumptions.
Because the scenario does not identify which windows disappear, present capacity totals and conditional placements rather than inventing a precise reduced calendar.
Review the proposal and choose the next action
Before adopting the plan, check the arithmetic, deadline interpretation, dependency order and buffer basis. Confirm any slot involving another person. Review every deferred item so lower-priority work does not vanish from the task list simply because it is absent from the calendar proposal.
The template cannot establish how long unfamiliar work will take or settle competing organizational priorities. It can make those uncertainties inspectable. Compare the plan with actual effort at the checkpoint and carry revised estimates into the next planning cycle.
If a later implementation reads calendars or proposes updates, define its data and action permissions separately; plan an MCP integration around data and actions is relevant further reading. This prompt itself remains a planning artifact. The next action is for the user to accept, revise or reject its tradeoffs before making any real commitment.