GPT 6 FIELDGUIDE
GPT 6 PROMPT

Plan a realistic week

Turn competing commitments into a humane weekly plan.

Independent resource

Complete prompt

Task
Turn competing commitments into a humane weekly plan.

Instructions
Plan my week from [COMMITMENTS], [FIXED EVENTS], [ENERGY PATTERN], and [ONE PRIORITY]. Separate fixed events from flexible work. Protect meals, sleep, and transition time. Offer a first draft, then list the two tradeoffs that matter most. Do not invent availability.

Expected output
A day-by-day table, assumptions, and two questions before any schedule is treated as final.

Checks
- All fixed events appear once.
- The plan contains buffers.
- Unknown availability is labeled.

Expected output and checks

Expected output

A day-by-day table, assumptions, and two questions before any schedule is treated as final.

Checks

  • All fixed events appear once.
  • The plan contains buffers.
  • Unknown availability is labeled.

Worked example

Plan a realistic week: recorded example

Codex · GPT-6 Astra · medium reasoning ·

Original input

Task
Turn competing commitments into a humane weekly plan.

Instructions
Plan my week from Synthetic week14–20 September2026. Flexible: budget review90min, write workshop handout120min, collect supplies60min. One instance each. Sleep23:00–07:00 daily; lunch12:00–13:00; dinner18:00–19:00; work tasks only09:00–17:00. Sunday afternoon availability is unknown., Monday09:00–10:00 team meeting; Wednesday14:00–15:00 hall visit with30min travel before and after; Saturday14:00–16:00 workshop with30min setup before and30min cleanup after. No other commitments., Best focused work Tuesday and Thursday mornings. Add15min transition buffers around work blocks., and Finish the workshop handout before Friday17:00.. Separate fixed events from flexible work. Protect meals, sleep, and transition time. Offer a first draft, then list the two tradeoffs that matter most. Do not invent availability.

Expected output
A day-by-day table, assumptions, and two questions before any schedule is treated as final.

Checks
- All fixed events appear once.
- The plan contains buffers.
- Unknown availability is labeled.

What the checks found

  • All three flexible tasks fit within 09:00–17:00; the handout is scheduled before its deadline. No scheduled block overlaps meals, sleep, travel or another task.
  • The first draft reserves Monday 08:45–09:00 as non-work transition time and explicitly asks whether that is acceptable. Sunday afternoon remains unused.

Revisions after the first output

  • No output edited. Treat the Monday buffer and supply-collection travel as two open scheduling choices.
Original output

This is a first draft for 14–20 September 2026, pending your answers below.

Every day: sleep 23:00–07:00, lunch 12:00–13:00, and dinner 18:00–19:00 are protected. Flexible work stays within 09:00–17:00.

Day Fixed events Flexible work and protected transitions
Monday 14 September Team meeting 09:00–10:00 Protect 08:45–09:00 and 10:00–10:15 as transitions; no flexible task scheduled.
Tuesday 15 September No fixed event beyond daily meals and sleep 09:00–09:15 transition; 09:15–11:15 write workshop handout (120 min); 11:15–11:30 transition.
Wednesday 16 September Hall visit 14:00–15:00; travel 13:30–14:00 and 15:00–15:30 Protect 13:15–13:30 and 15:30–15:45 as transitions; no flexible task scheduled.
Thursday 17 September No fixed event beyond daily meals and sleep 09:00–09:15 transition; 09:15–10:45 budget review (90 min); 10:45–11:00 transition.
Friday 18 September No fixed event beyond daily meals and sleep 13:00–13:15 transition; 13:15–14:15 collect supplies (60 min); 14:15–14:30 transition.
Saturday 19 September Setup 13:30–14:00; workshop 14:00–16:00; cleanup 16:00–16:30 Protect 13:15–13:30 and 16:30–16:45 as transitions around the complete event block.
Sunday 20 September No fixed event beyond daily meals and sleep No work scheduled. Afternoon availability unknown; this draft does not rely on it.

Assumptions

  • “Work tasks only 09:00–17:00” applies to active tasks; Monday’s 08:45 transition is protected preparation-free time, not extra work.
  • Setup, workshop, and cleanup form one continuous fixed event; the Wednesday travel and visit similarly form one continuous block. Buffers sit outside these blocks.
  • Each flexible task occurs once. The handout finishes Tuesday, ahead of Friday 17:00. Supply collection’s 60 minutes is provisionally treated as the full task, including any travel; extra travel has not been invented.
  • Unassigned time stays unassigned; Sunday afternoon is not assumed available.

The two tradeoffs that matter most

  1. Using Tuesday and Thursday mornings for the handout and budget protects your strongest focus time, but leaves less of that time for anything unexpected.
  2. Friday supply collection keeps the earlier week light, but leaves little recovery time if supplies are unavailable before Saturday.

Two questions before finalizing

  1. Does the 60-minute supply collection estimate include travel, and would you prefer it earlier in the week to allow time for shortages?
  2. Is a protected 08:45–09:00 transition acceptable on Monday, or does the 09:00 boundary also prohibit reserving transition time before work?

Files from this run