Context Switch Budget Skill
The calendar shows eight meetings totaling four hours and calls the other four "free" — but fifteen-minute gaps between meetings are free the way confetti is paper: technically yes, usable no. Each switch costs re-entry time (the mind reloads the last context for 10–20 minutes), and a day of eight switches can contain zero real work while looking half-empty. The budget discipline: census the week's actual switches (the number shocks reliably), batch the same-kind work (meetings to meeting-blocks, reviews to review-hours, chat to email-triage-system-style windows), defrag the calendar (consolidate the gaps into slabs worth having), and price new fragmentation at the door.
What This Skill Produces
- The switch census — the week's transitions counted and typed (meeting↔work, task↔task, interrupt-driven), with the fragmentation map
- The batching plan — same-kind work consolidated: the meeting corridors, the review hour, the comms windows
- The defrag moves — the specific reschedules that convert cheese-holes into slabs (deep-work-blocking receives them)
- The door pricing — the phrases that protect the defragged shape ("Tuesday corridor?" as the default counter-offer)
Required Inputs
Ask for these if not provided:
- A real week's calendar — last week, as it actually ran (including the unscheduled interruptions the user remembers); the census works on evidence
- The work's kinds — what recurs: meetings, reviews, writing, admin, comms; batching needs the categories named
- The movable vs. fixed — which meetings the user controls or can counter-propose (recurring-meeting-pruner verdicts feed this), and the team's collaboration-hours constraints
- The interrupt sources — what punches through ad hoc (chat, drive-bys, "quick calls") — each gets a batching destination or a boundary
Framework: The Budget Rules
- Census first — the number is the intervention: count last week's switches (every transition between unlike work counts; every meeting-to-meeting gap under 30 minutes counts as a lost slab). The typical knowledge-week runs 30–50; seeing "41 switches, longest unbroken stretch: 52 minutes" reframes the problem from "I'm unproductive" to "my week is structurally incapable of depth" — which is true, and fixable.
- Batch by kind, on a rhythm: meetings compress into corridors (Tue/Thu afternoons — the counter-offer default) · reviews/approvals into a daily half-hour · comms into 2–3 windows · admin into one Friday hour. Same-kind work shares context; batching converts eight reloads into one.
- Defrag the residue: the gaps that remain after batching get consolidated — the two 45-minute holes become one 90-minute slab by moving one meeting ("could we do 2pm instead of 3?"— movers rarely mind, they just never think to ask). Slabs go to the deep-work design; the census re-runs in two weeks to verify the shape held.
- Interrupts get destinations, not resistance: the chat that punches through routes to the comms windows (with the office-hours-design never-waits line honored) · drive-bys get the warm deferral ("in the middle of a thing — grab me at 3?") · the genuinely-urgent keeps its lane, defined. Fighting interrupts case-by-case loses; routing them by class holds.
- Price fragmentation at the door: every incoming meeting request gets the corridor counter-offer by default ("Could this land Tuesday PM? I batch meetings there") — most acceptors don't care where, so the asker's shape wins by initiative. The switch-cost line, for when justification helps: "a 3pm call splits my only deep block — the 10am corridor keeps me sharp for it anyway."
Output Format
Switch Budget: [name] — last week: [N] switches, longest slab: [T]
The Census
[Switches by type · the fragmentation map (the week's shape drawn) · the shock number stated plainly]
The Batching Plan
| Work kind |
Batch destination |
Cadence |
| [Meeting corridors · review hour · comms windows · admin hour] |
|
|
The Defrag Moves
[The specific reschedules → the slabs created → assigned to (deep-work blocks)]
Door Pricing
[The corridor counter-offer, verbatim · the interrupt routing by class · the re-census date (T+2 weeks)]
Quality Checks
Anti-Patterns
1---2name: context-switch-budget3description: Treat context switches as the budget line they are — the switch census (how fragmented the week really is), the batching moves that consolidate scattered same-kind work, the calendar defrag that turns Swiss cheese into slabs, and the switch-cost line for saying no. Use when asked my day is fragmented to death, count my context switches, batch my meetings and reviews, or defend against calendar Swiss cheese. Produces the fragmentation census, the batching plan, the defrag moves, and the protective phrases.4---5
6# Context Switch Budget Skill
7
8The calendar shows eight meetings totaling four hours and calls the other four "free" — but fifteen-minute gaps between meetings are free the way confetti is paper: technically yes, usable no. Each switch costs re-entry time (the mind reloads the last context for 10–20 minutes), and a day of eight switches can contain zero real work while looking half-empty. The budget discipline: *census* the week's actual switches (the number shocks reliably), *batch* the same-kind work (meetings to meeting-blocks, reviews to review-hours, chat to [email-triage-system](../email-triage-system/SKILL.md)-style windows), *defrag* the calendar (consolidate the gaps into slabs worth having), and price new fragmentation at the door.
9
10## What This Skill Produces
11
12- **The switch census** — the week's transitions counted and typed (meeting↔work, task↔task, interrupt-driven), with the fragmentation map
13- **The batching plan** — same-kind work consolidated: the meeting corridors, the review hour, the comms windows
14- **The defrag moves** — the specific reschedules that convert cheese-holes into slabs ([deep-work-blocking](../deep-work-blocking/SKILL.md) receives them)
15- **The door pricing** — the phrases that protect the defragged shape ("Tuesday corridor?" as the default counter-offer)
16
17## Required Inputs
18
19Ask for these if not provided:
20- **A real week's calendar** — last week, as it actually ran (including the unscheduled interruptions the user remembers); the census works on evidence
21- **The work's kinds** — what recurs: meetings, reviews, writing, admin, comms; batching needs the categories named
22- **The movable vs. fixed** — which meetings the user controls or can counter-propose ([recurring-meeting-pruner](../recurring-meeting-pruner/SKILL.md) verdicts feed this), and the team's collaboration-hours constraints
23- **The interrupt sources** — what punches through ad hoc (chat, drive-bys, "quick calls") — each gets a batching destination or a boundary
24
25## Framework: The Budget Rules
26
271. **Census first — the number is the intervention:** count last week's switches (every transition between unlike work counts; every meeting-to-meeting gap under 30 minutes counts as a lost slab). The typical knowledge-week runs 30–50; seeing "41 switches, longest unbroken stretch: 52 minutes" reframes the problem from "I'm unproductive" to "my week is structurally incapable of depth" — which is true, and fixable.
282. **Batch by kind, on a rhythm:** meetings compress into corridors (Tue/Thu afternoons — the counter-offer default) · reviews/approvals into a daily half-hour · comms into 2–3 windows · admin into one Friday hour. Same-kind work shares context; batching converts eight reloads into one.
293. **Defrag the residue:** the gaps that remain after batching get consolidated — the two 45-minute holes become one 90-minute slab by moving one meeting ("could we do 2pm instead of 3?"— movers rarely mind, they just never think to ask). Slabs go to the deep-work design; the census re-runs in two weeks to verify the shape held.
304. **Interrupts get destinations, not resistance:** the chat that punches through routes to the comms windows (with the [office-hours-design](../office-hours-design/SKILL.md) never-waits line honored) · drive-bys get the warm deferral ("in the middle of a thing — grab me at 3?") · the genuinely-urgent keeps its lane, defined. Fighting interrupts case-by-case loses; routing them by class holds.
315. **Price fragmentation at the door:** every incoming meeting request gets the corridor counter-offer *by default* ("Could this land Tuesday PM? I batch meetings there") — most acceptors don't care where, so the asker's shape wins by initiative. The switch-cost line, for when justification helps: "a 3pm call splits my only deep block — the 10am corridor keeps me sharp for it anyway."
32
33## Output Format
34
35# Switch Budget: [name] — last week: [N] switches, longest slab: [T]
36
37## The Census
38[Switches by type · the fragmentation map (the week's shape drawn) · the shock number stated plainly]
39
40## The Batching Plan
41| Work kind | Batch destination | Cadence |
42|---|---|---|
43[Meeting corridors · review hour · comms windows · admin hour]
44
45## The Defrag Moves
46[The specific reschedules → the slabs created → assigned to (deep-work blocks)]
47
48## Door Pricing
49[The corridor counter-offer, verbatim · the interrupt routing by class · the re-census date (T+2 weeks)]
50
51## Quality Checks
52
53- [ ] The census counted a real week, including sub-30-minute gaps as losses
54- [ ] Every recurring work-kind has a batch destination
55- [ ] Defrag moves are specific reschedules, not aspirations
56- [ ] Interrupt classes route somewhere legitimate
57- [ ] The re-census is scheduled to verify the shape held
58
59## Anti-Patterns
60
61- [ ] Do not read gap-time as free time — confetti isn't paper you can write on
62- [ ] Do not fight interrupts individually — route classes; case-by-case is whack-a-mole with your attention
63- [ ] Do not accept meeting times passively — the counter-offer wins by default because nobody else is playing
64- [ ] Do not batch into your peak hours — corridors go on the energy map's shoulders; peaks are for slabs
65- [ ] Do not defrag once — calendars re-fragment on schedule; the re-census is the maintenance
gabrielmoreira