How to Plan Your Week from a Messy Calendar Dump

Anyone staring at a calendar export can plan a week from a messy dump in 20 minutes: extract only real events, name five work blocks, park the overflow, and protect one empty afternoon. Run it in ChatGPT, Claude, or Gemini before the model invents a “focus sprint” you never booked.

The dump is not the plan. The dump is a pile of invitations, ghosts, and hope. Your job is to force a week a future you can actually walk.

If you paste “make me a productive week” into a blank chat, you will get a self-help poster. Turn this into a skill. Read what a skill prompt actually is, then run the extract-then-cap loop below.

Extract, then cap, then plan the week

Do not ask for a plan in the first message. A first-message plan is how ChatGPT hallucinates a Tuesday workshop that was a declined invite.

1. Dump raw, then demand a mirror

Paste the export, the screenshot OCR, the notes app list. Instruct: “Do not clean this. Do not add events. Repeat back only timed items I provided, as a bullet list with day, start, end, and title in my words.”

Hold the model to a mirror. If a title gets prettier, the session is already lying.

This is the same dump-first move as turning a messy note into a one-page brief. Shape comes after the mirror, never inside it.

2. Tag each item: REAL, TENTATIVE, or JUNK

You tag. The model proposes, you confirm.

• REAL: you will attend or you already accepted.
• TENTATIVE: you might move it. It does not get a work block yet.
• JUNK: declined, duplicate, “hold,” or a notification that is not a meeting.

Instruct: “Label each mirrored item. If you are not sure, mark UNKNOWN. Do not promote UNKNOWN to REAL.”

UNKNOWN stays visible. Promotion is how a maybe becomes a 9 a.m.

3. Name five work blocks, not a color-coded life

One verb-plus-object per block. “Write the Q3 brief.” “Close two invoices.” Not “deep work” and not “admin.”

Five. Across the whole week. Not five per day.

Tell Claude, ChatGPT, or Gemini: “Place only these five blocks in open gaps between REAL events. Each block needs a start, an end, and a day. If a block does not fit, write PARKED. Do not shrink REAL events to make room.”

Shrinking someone else’s meeting to fit your ambition is fiction.

4. Protect one empty afternoon

Pick the afternoon yourself. Label it EMPTY. No suggestions inside it.

“If you schedule EMPTY, you failed. If you ‘softly suggest’ a catch-up for EMPTY, you failed. Print the hole.”

This is the same empty-block law as planning a weekend trip without a generic itinerary. Full days are how plans die on Wednesday.

5. One human pass, then save the loop

Read the week out loud, Monday to Friday. Check three traps:

• A work block that overlaps a REAL event.
• A TENTATIVE that quietly became REAL.
• A sixth block hiding as “quick win.”

Fix those in your words. Send: “Replace only the lines I changed. Do not re-expand. Do not add evening routines.”

Evening routines are a second plan. You asked for a week from a dump, not a lifestyle.

Save the extract-tag-cap-empty loop, not this week’s titles. Put it in the Promptcrates tools for reusable skills so next Monday’s dump does not start from “make me productive.”

Reusable skill card

Trigger: You just exported a calendar or pasted a week of chaos into ChatGPT, Claude, or Gemini and you can already see a fake focus sprint.

Input: The raw dump, one time zone, five named work blocks, and one afternoon you already chose as EMPTY.

Output: A mirrored event list, REAL/TENTATIVE/JUNK tags, five placed blocks or PARKED, EMPTY left blank, no invented meetings.

Stop: After one read-aloud pass. No evening routine. No sixth block. No motivational closer.

Takeaways

• Mirror the dump first. A first-message plan invents meetings.
• You tag REAL, TENTATIVE, JUNK. The model does not promote.
• Five work blocks for the week. Overflow is PARKED.
• One EMPTY afternoon, printed as a hole.
• Save the loop as a skill. This week’s titles are disposable.