Deep Work Blocking

---
name: deep-work-blocking
description: "Protect focus time that actually survives the week — the block placement matched to real energy hours, the defense rules (what moves a block, what never), the entry ritual that beats the blank-stare start, and the honest sizing that stops 8-hour fantasy blocks. Use when asked block focus time that keeps getting eaten, when should I schedule deep work, my calendar has no room to think, or I block time and then waste it. Produces the block design, the defense tiers, the entry ritual, and the meeting-culture negotiation."
---

# Deep Work Blocking Skill

Focus blocks fail three ways: placed wrong (2pm slump hosting the hardest work), defended badly (the block that moves for every invite is decoration with a border color), and entered badly (twenty minutes of warmup-shuffling inside a 90-minute block is a 70-minute block wearing a lie). The design fixes all three: blocks land on the user's *actual* high-energy hours ([energy-scheduling](../energy-scheduling/SKILL.md) supplies the map), carry explicit defense tiers (what outranks them — almost nothing — and the decline scripts), and start with an entry ritual — the named task waiting, the environment pre-set — because a block is a container, and containers need contents chosen *before* the clock starts.

## What This Skill Produces

- **The block design** — count, length (90–120 min beats the 8-hour fantasy), and placement on real energy hours
- **The defense tiers** — what moves a block (genuine emergencies, defined), what never does, and the decline scripts
- **The entry ritual** — the task named the day before, the environment checklist, the first-five-minutes rule
- **The culture negotiation** — making blocks legible to the team (the shared norm beats the solo fight)

## Required Inputs

Ask for these if not provided:
- **The energy reality** — when the user's genuinely sharp hours fall (the honest answer, not the aspirational one); blocks on slump hours produce guilt, not work
- **The calendar's constraints** — the immovable meetings, the team's collaboration hours, the time zone spread; blocks live in the real grid
- **The work that needs the blocks** — the big-three outcomes ([weekly-review-ritual](../weekly-review-ritual/SKILL.md)) the blocks exist to serve; blocks without assigned work become email time with the door closed
- **The interruption culture** — can a block survive here socially? The negotiation section scales to the actual environment

## Framework: The Blocking Rules

1. **Size honestly, place on peaks:** 90–120 minutes is the sustainable unit (attention's real budget); two such blocks is a strong day. The 8-hour focus fantasy collapses by 11am and discredits the practice. Placement follows the energy map — the best hours go to the hardest work *first*, before the calendar's entropy claims them ([recurring-meeting-pruner](../recurring-meeting-pruner/SKILL.md) reclaims supply this space).
2. **Defense tiers, pre-decided:** Tier 1 (never moves): the two weekly anchor blocks — invites get the script: "I have a commitment then — Thursday 2pm works?" (a block IS a commitment; the script just declines to itemize it). Tier 2 (moves for named things): the flex blocks, moved *forward in the same week*, never deleted. The emergency definition is written: production-down and boss-says-now qualify; "quick sync?" does not.
3. **The entry ritual kills the warmup tax:** the day before, the block gets its *named task* ("draft sections 2–3," not "work on the doc") · entry checklist: notifications off, the one document open, phone elsewhere · the first-five-minutes rule: start on the named task immediately, badly if necessary — momentum converts; browsing "to warm up" evaporates blocks whole.
4. **Blocks are legible, not secret:** the calendar shows "Focus block" (visible, normalized), the team knows the pattern ("mornings I'm deep, afternoons I'm reachable" — [working-agreements](../working-agreements/SKILL.md) material), and the async norms ([async-update-format](../async-update-format/SKILL.md)) carry what would have interrupted. The solo fight against a synchronous culture loses; the negotiated norm holds.
5. **The block reviews itself:** each block ends with 60 seconds — did the named task move? If blocks keep producing nothing, the diagnosis tree runs: wrong hours (re-place), wrong sizing (shrink), vague tasks (the naming discipline), or leaks (the defense failed — count what actually interrupted). Blocks that fail silently get quietly deleted by their owner within a month; the review is the early-warning.

## Output Format

# Deep Work Design: [name] — [N] blocks/week

## The Blocks
[Day × time × tier · placed on: (the energy map's peaks) · serving: (the big three)]

## Defense
[Tier 1 anchors + the decline script · Tier 2 flex + the same-week-move rule · the written emergency definition]

## The Entry Ritual
[Named-task-the-day-before · the environment checklist · the first-five-minutes rule]

## The Culture Layer
[The calendar's public label · the team norm proposed · where the interruptions route instead]

## Quality Checks

- [ ] Blocks are 90–120 min on honest energy peaks
- [ ] Every block has a tier and the scripts exist
- [ ] Tomorrow's block already has its named task
- [ ] The team-legibility norm is proposed, not just personal stealth
- [ ] The 60-second self-review closes each block

## Anti-Patterns

- [ ] Do not block the fantasy 8 hours — two real units beat one heroic collapse
- [ ] Do not place deep work on slump hours because they're free — free and useless is why they're free
- [ ] Do not enter without a named task — an unassigned block is email with ambiance
- [ ] Do not defend by itemizing — "I have a commitment" is complete; justification invites negotiation
- [ ] Do not fight the culture solo forever — the negotiated norm is the sustainable version of the fight