deep-work — Claude Code plugin: time-block your day
Turns a task list into a time-blocked day with deep blocks, a shallow-work budget and focus-hour tracking.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install deep-work@claude-code-skillsWhat deep-work does
The plugin sorts every task into deep or shallow, checks the shallow share against a budget, and places deep blocks in the earliest hours. That budget defaults to 50%, and when your list goes over it the auditor exits with code 2 and names what to cut.
The planner enforces a hard ceiling: more than 4 hours of deep work is refused. Shallow tasks get batched into at most two windows, 10-minute buffers sit between blocks to drain attention residue, lunch is fixed, and the hard stop never quietly slides — overflow comes back as a named refusal. Three stdlib Python scripts do the arithmetic: shallow_work_auditor.py, time_block_planner.py and focus_session_logger.py. The logger keeps a JSON ledger of sessions and reports weekly deep hours against your target plus a consecutive-day streak.
You get a skill, an agent, the commands /cs-deep-work and /cs-time-block, reference notes and a shutdown-ritual checklist. It plans one person's attention across a day and a week, so team capacity and sprint math stay out of scope — for that, look at project-management.
What it helps with
- lay out a task list across the day without overloading it
- measure the shallow share and trim it to the budget
- protect early hours for long focus blocks
- track weekly deep hours and a day streak
- close the day with a shutdown ritual instead of drifting
Example prompts for the agent
- plan my deep work day: write the spec, clear email, team call
- /cs-time-block from my task list for today
- /cs-deep-work — plan the day and audit my shallow-work budget
How to install deep-work
Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install deep-work@claude-code-skillsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about deep-work
How do I install deep-work in Claude?
Add the marketplace with /plugin marketplace add alirezarezvani/claude-skills, then install the plugin: /plugin install deep-work@claude-code-skills.
What does deep-work do?
It classifies tasks as deep or shallow, audits the shallow share against a budget, and builds a time-blocked schedule. A separate logger tracks focus sessions against a weekly target and a streak.
What happens if deep work exceeds 4 hours?
The planner refuses to build that day and exits with code 2, naming the tasks to defer or shorten.
Source text
deep-work · MIT
# deep-work — Time-Block the Day, Budget the Shallow > Plan a deep work day the Cal Newport way. Attention is the protected resource, not time. `/deep-work` turns a raw task list into a time-blocked day: every task classified deep vs shallow, the shallow share audited against a budget, deep blocks of at least 90 minutes placed in the earliest hours under a hard **4-hour ceiling**, shallow work batched into at most two windows, and the day closed with a shutdown ritual. A local ledger tracks weekly deep hours and streaks. ## The discipline | Rule | Enforced by | |---|---| | Shallow work gets a budget (default 50%) before anything is scheduled | `shallow_work_auditor.py` — OVER-BUDGET exits 2 | | Deep blocks: ≥90 minutes, earliest hours, energy-first | `time_block_planner.py` | | Deep demand past 4 hours is refused, naming what to defer | `time_block_planner.py` — exit 2 | | Shallow work: at most two batches (late morning + end of day) | `time_block_planner.py` | | 10-minute buffers drain attention residue between blocks | `time_block_planner.py` | | The hard stop never silently extends — overflow is refused by name | `time_block_planner.py` — exit 2 | | Deep hours are measured, not felt | `focus_session_logger.py` — status / streak | | The day ends with a shutdown ritual, not a fade-out | `assets/shutdown_checklist.md` | ## Quick start ```bash # 1. Audit the task list — deep vs shallow, share vs budget python skills/deep-work/scripts/shallow_work_auditor.py --sample # 2. Build the time-blocked day (refuses >4h deep, refuses overflow) python skills/deep-work/scripts/time_block_planner.py --sample # 3. Log real focus sessions; check the weekly target and streak python skills/deep-work/scripts/focus_session_logger.py log --minutes 90 --label "Write spec" python skills/deep-work/scripts/focus_session_logger.py status --target 15 ``` Or just say **"plan my deep work day: …"**, run `/cs-deep-work` (full workflow), or `/cs-time-block` (quick plan from a task list). ## What's in the box - **Skill:** [`skills/deep-work/SKILL.md`](skills/deep-work/SKILL.md) - **Agent:** [`agents/cs-deep-work.md`](agents/cs-deep-work.md) - **Commands:** [`commands/cs-deep-work.md`](commands/cs-deep-work.md) — `/cs-deep-work`; [`commands/cs-time-block.md`](commands/cs-time-block.md) — `/cs-time-block` - **3 stdlib scripts:** `shallow_work_auditor.py`, `time_block_planner.py`, `focus_session_logger.py` - **3 references** (6-7 sources each: Newport, Leroy, Mark, Ericsson, Csikszentmihalyi, Graham, Gollwitzer, Eyal, Parkinson, Zeigarnik, Masicampo & Baumeister, Perlow, RescueTime, Atlassian), **2 assets** (worked example day + shutdown-ritual checklist) ## Not the same as - **`productivity/andreessen`** — the 3x5 card picks WHAT matters today. Deep-work plans WHEN and HOW, with attention protected. Run the card first, then block the day here. - **`project-management` capacity planning** — team-level capacity and sprint math. This is one person's attention across one day and one week. - **`productivity/reflect`** — end-of-week reflection prose. The shutdown ritual here is a daily, mechanical close. ## License MIT.
© Alireza Rezvani · MIT · alirezarezvani/claude-skills
