Deep work planner
Designs a daily schedule that protects deep work - classifies tasks as deep or shallow, places 2-4 focus blocks of 60-120 minutes at peak energy hours, batches shallow work into fixed windows, and defines each session with a goal, definition of done, distraction plan, and first action, plus startup/shutdown rituals and a weekly scorecard. Use when someone says "I can't get any focused work done", "plan my day around deep work", "how do I stop context switching", or wants to defend calendar time for demanding work. Do NOT use for processing an email backlog - use inbox-zero instead - or for a full task-capture system - use gtd-system instead.From its SKILL.md
npx -y skills add SkillMedev/skills --skill deep-work-plannerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.1 KB, 586 tokens by cl100k_base, as published. Nobody here has run it
Deep Work Planner
Deep work is cognitively demanding work done without distraction. It produces disproportionate value. This skill helps you protect and design it.
Step 1: Classify your tasks
Sort the day's tasks into two lists:
- Deep - requires sustained focus, creates new value, hard to replicate (writing, designing, coding hard logic, strategy).
- Shallow - logistical, low-concentration, often interrupt-driven (email, Slack, scheduling, quick reviews).
Step 2: Schedule deep blocks
- Place 2-4 deep blocks of 60-120 minutes at your peak energy hours (for most people, the first hours after starting).
- Block them on the calendar as real events - defend them like meetings.
- Single-task: one project per block. No context switching mid-block.
- Cap deep work at ~4 hours/day; it is a finite daily resource.
Step 3: Batch the shallow
- Collect shallow tasks into 1-2 fixed windows (e.g. 11:30 and 16:30).
- Communicate your async hours so people know when to expect replies.
- Anything under 2 minutes during a batch window: just do it.
Step 4: Design the session
For each deep block, define before you start:
Block: <time range>
Goal: <one concrete deliverable>
Definition of done: <how you'll know you're finished>
Distraction plan:
- Phone: in another room / focus mode
- Notifications: off
- Tabs: only what's needed
First action: <the very first move so you don't stall>
Focus rituals
- Startup ritual: clear desk, water nearby, close comms, write the goal at the top.
- The 5-minute rule: when the urge to switch hits, commit to 5 more minutes first.
- Shutdown ritual: at day's end, review what shipped, plan tomorrow's first block, then disconnect completely.
Energy management
- Match task type to energy: deep work at peaks, shallow at troughs.
- Take a real break between deep blocks (walk, no screens) - focus needs recovery.
- Protect sleep; deep work quality collapses when under-rested.
Weekly scorecard
Track and review each week:
- Deep hours completed vs. planned.
- Biggest distraction source - eliminate one per week.
- Best deliverable produced in deep time.
Anti-patterns
- "I'll focus when I get a free moment" - free moments never come; schedule it.
- Checking messages inside a deep block - even a glance costs 20+ min of refocus.
- Stacking back-to-back deep blocks with no recovery - quality decays fast.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most plan spec skills give in 586 tokens
Counted across 1,099 of the 1,860 authors here whose files we hold, read 2026-08-07
- Ask one question at a timein 51 of 1099
- Break plans into vertical slicesin 29 of 1099, across 11 files
- Publish issues in dependency orderin 27 of 1099, across 9 files
- Iterate until user approves the breakdownin 25 of 1099, across 7 files
- Explore the repository to understand the codebase statein 24 of 1099, across 7 files
- Use domain glossary vocabularyin 23 of 1099, across 5 files
- Apply correct triage labels to published issuesin 23 of 1099, across 5 files
- Prefer AFK slices over HITLin 22 of 1099, across 7 files
- Write a specification before writing any codein 22 of 1099, across 14 files
- Write failing tests before implementation codein 22 of 1099, across 20 files
- Ask clarifying questions until requirements are concretein 21 of 1099, across 13 files
- Respect existing architecture decision recordsin 20 of 1099, across 5 files
Said here and by no other author read
- Classify tasks as deep or shallow
- Schedule 2-4 deep blocks during peak energy
- Block deep work on the calendar
- Single-task within each block
- Batch shallow tasks into fixed windows
- Define a goal for each deep block
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.