deep-work

Topics in the source

• Deep Work — Time-Block the Day, Budget the Shallow
• What this does
• Step 1 — Classify and budget the shallow
• Step 2 — Block the day
• Step 3 — Log the session, keep the streak
• Step 4 — Shutdown ritual
• Scripts
• References

Portability: Reasoning-led skill with 3 stdlib Python scripts. No external APIs, no LLM calls in scripts. Works in Claude Code CLI and Claude.ai web. The scripts fix the arithmetic; you keep the judgment. A calendar full of reactions is not a plan. This skill turns a raw task list into a day where attention is the protected resource: deep tasks get the earliest hours in blocks of at least 90 minutes, shallow work is batched into at most two windows, buffers absorb attention residue, and the schedule flatly refuses more than 4 hours of deep demand — the trained daily ceiling. A local ledger of focus sessions keeps the weekly deep-hours target measured, not felt. Ask for today's task list with rough minutes per task (or take it from $ARGUMENTS). The auditor classifies each task deep vs shallow (keyword heuristics; an explicit :deep/:shallow suffix always wins), computes the shallow share against the budget, and prints the forcing question for every shallow item — how long would it take to train a smart recent graduate to do this? OVER-BUDGET (exit 2) means cut, batch, or delegate before any schedule is built. Feed the surviving tasks to the planner with the day's hard start and hard

This is an excerpt. Refer to the complete source and its current requirements.