Time-Blocked Daily Planner

Plan a working day as a sequence of committed blocks rather than a list of hopes. The rules that make time-blocking survive contact with a real Tuesday: fixed commitments are terrain, one task is crowned the day's must-move, estimates get buffers because estimates lie, and the day ends with a shutdown ritual instead of a fade-out. Plan about seventy percent of available time; a day planned to one hundred percent is dead by mid-morning.

When to use this skill

The user asks to plan their day, "time-block tomorrow", or turn a task list into a schedule
Busy days keep ending with the important thing untouched
A calendar full of meetings leaves fragments that keep evaporating
Someone wants a repeatable daily planning ritual, morning or night-before
Deep work keeps losing to reactive work and the user wants structure to defend it

Intake

Collect, or ask for, five things: today's fixed commitments with times; the task list with rough estimates; any hard deadlines; when the user's energy peaks and dips; and the honest start and stop times of the working day — the planned day ends at a chosen hour, not at collapse.

Workflow

Place fixed commitments on the timeline first. Meetings and appointments are terrain, not tasks — the plan is built around them, and a 15-minute gap is inserted after each one, because meetings leak.
Crown the must-move: the single task that makes the day a success if nothing else happens. It gets the best energy slot of the day — not the first free slot, the best one.
Schedule one or two deep work blocks of 90 minutes maximum. Longer blocks feel heroic in the plan and die in practice. Each block does one named thing; "work on project" is not a block, it is a wish.
Batch the shallow work — messages, small admin, quick replies — into two defined blocks, typically late morning and late afternoon. Sprinkled shallow work is how deep blocks get eaten from the edges.
Buffer honestly: add 25 to 50 percent to every estimate, and leave visible white space. Lunch is a block. The buffer is not slack to be optimized away; it is what makes the rest of the plan true.
Match work to energy: hard creative work at the peak, mechanical and administrative work in the dip. Fighting biology with willpower loses on schedule.
End with a 15-minute shutdown block: mark what moved, visibly reschedule what did not, write tomorrow's must-move while context is warm, close open loops with two-line replies, and stop on purpose.

Day template

08:30  Plan review + must-move confirmation        (10 min)
08:40  DEEP BLOCK 1 — must-move task               (90 min)
10:10  Buffer / walk                                (15 min)
10:25  Shallow batch 1 — messages, small items      (35 min)
11:00  Meeting (fixed)                              (60 min)
12:00  Gap after meeting                            (15 min)
12:15  Lunch — a block, not a maybe                 (45 min)
13:00  DEEP BLOCK 2 — second priority               (90 min)
14:30  Buffer                                       (15 min)
14:45  Low-energy lane — admin, reviews, errands    (60 min)
15:45  Shallow batch 2 + tomorrow's loose ends      (45 min)
16:30  Shutdown ritual                              (15 min)
16:45  Done. Actually done.

Adapt times to the user's terrain; keep the shapes — two deep blocks, two shallow batches, buffers after meetings, a real lunch, a real shutdown.

Rules

A block does one thing; multitasking inside a block is the block failing quietly
When an interruption wins, renegotiate visibly — move the block, never pretend it happened
Tasks without estimates do not get blocks; estimate them or break them down first
A task that overflows its block three days running has a lying estimate — fix the estimate, not the willpower
Protect deep blocks mechanically: notifications off, status set, door metaphorically shut

Quality bar

No more than seventy percent of available time is scheduled
The must-move sits in the user's stated peak-energy slot
Every meeting is followed by a gap; every estimate carries its buffer
The plan ends with a shutdown block and a written must-move for tomorrow
The whole plan fits on one screen and can be rebuilt in five minutes when the day explodes