assets/example_time_block_plan.md
3.9 KB查看排版效果| 1 | # Worked Example — A Full Deep-Work Day (Audit → Plan → Mid-Day Revision → Shutdown) |
| 2 | |
| 3 | > A complete pass through the `deep-work` skill for one realistic day, showing the exact script |
| 4 | > invocations and their outputs, including the mid-day revision that every real day eventually needs. |
| 5 | |
| 6 | ## The raw task list (as the user gave it) |
| 7 | |
| 8 | - Write the Q3 product spec — ~2h, the week's most important output |
| 9 | - Design the onboarding flow — ~1.5h |
| 10 | - Email sweep — 30 min |
| 11 | - Team status update — 20 min |
| 12 | - Expense report — 15 min |
| 13 | |
| 14 | Day: 08:30 hard start, 17:00 hard stop, lunch 12:30. |
| 15 | |
| 16 | ## Step 1 — Shallow audit |
| 17 | |
| 18 | ```bash |
| 19 | python scripts/shallow_work_auditor.py \ |
| 20 | --task "Write Q3 product spec:120" \ |
| 21 | --task "Design onboarding flow:90" \ |
| 22 | --task "Email sweep:30" \ |
| 23 | --task "Team status update:20" \ |
| 24 | --task "Expense report:15" \ |
| 25 | --budget 50 |
| 26 | ``` |
| 27 | |
| 28 | Result: `Write Q3 product spec` and `Design onboarding flow` classify DEEP (write/design signals); |
| 29 | the other three classify SHALLOW (email/status/expense signals). Shallow share = 65 of 275 min = |
| 30 | **23.6% vs a 50% budget → WITHIN-BUDGET (exit 0)**. The forcing question printed for each shallow |
| 31 | item confirmed none of them deserves a promotion to deep. Proceed. |
| 32 | |
| 33 | ## Step 2 — The plan |
| 34 | |
| 35 | ```bash |
| 36 | python scripts/time_block_planner.py --start 08:30 --end 17:00 --lunch 12:30 \ |
| 37 | --task "Write Q3 product spec:120:deep" \ |
| 38 | --task "Design onboarding flow:90:deep" \ |
| 39 | --task "Email sweep:30:shallow" \ |
| 40 | --task "Team status update:20:shallow" \ |
| 41 | --task "Expense report:15:shallow" |
| 42 | ``` |
| 43 | |
| 44 | | Start | End | Block | Mode | |
| 45 | |-------|-----|-------|------| |
| 46 | | 08:30 | 10:30 | DEEP — Write Q3 product spec | DEEP | |
| 47 | | 10:30 | 10:40 | Buffer — stand up, reset | BUFFER | |
| 48 | | 10:40 | 12:10 | DEEP — Design onboarding flow | DEEP | |
| 49 | | 12:10 | 12:20 | Buffer — stand up, reset | BUFFER | |
| 50 | | 12:20 | 12:30 | Flex — reset, no inputs | FLEX | |
| 51 | | 12:30 | 13:00 | Lunch — away from the desk | BREAK | |
| 52 | | 13:00 | 13:50 | SHALLOW batch (late morning) — Email sweep · Team status update | SHALLOW | |
| 53 | | 13:50 | 16:45 | Flex — overflow absorber | FLEX | |
| 54 | | 16:45 | 17:00 | SHALLOW batch (end of day) — Expense report | SHALLOW | |
| 55 | |
| 56 | Deep 3h30 / 4h cap · Shallow 1h05 · Flex 3h05 · Buffers 20min |
| 57 | |
| 58 | Reading the plan: both deep blocks own the morning — the best hours — before the manager-schedule |
| 59 | world wakes up. Shallow work exists in exactly two windows. The big afternoon flex block is not |
| 60 | waste; it is where meetings, overruns, and surprises land without touching the deep blocks. |
| 61 | |
| 62 | ## The revision (because the day broke, as days do) |
| 63 | |
| 64 | At 10:15 an incident call ate the rest of the spec block. The rule: **revise, don't abandon.** |
| 65 | At 11:00, re-plan the remaining day with what actually survives: |
| 66 | |
| 67 | ```bash |
| 68 | python scripts/time_block_planner.py --start 11:00 --end 17:00 --lunch 12:30 \ |
| 69 | --task "Finish Q3 product spec:90:deep" \ |
| 70 | --task "Email sweep:30:shallow" \ |
| 71 | --task "Team status update:20:shallow" \ |
| 72 | --task "Expense report:15:shallow" |
| 73 | ``` |
| 74 | |
| 75 | The onboarding-flow design moved to tomorrow's first block — named and deferred, not silently |
| 76 | squeezed into the evening. The redrawn day still has one protected 90-minute deep block, and the |
| 77 | hard stop did not move. |
| 78 | |
| 79 | ## Step 3 — Log what actually happened |
| 80 | |
| 81 | ```bash |
| 82 | python scripts/focus_session_logger.py log --minutes 75 --label "Q3 product spec (pre-incident)" |
| 83 | python scripts/focus_session_logger.py log --minutes 90 --label "Q3 product spec (finish)" |
| 84 | python scripts/focus_session_logger.py status --target 15 |
| 85 | ``` |
| 86 | |
| 87 | 2h45 banked today. The week's ledger, not memory, decides whether the 15-hour target is on track. |
| 88 | |
| 89 | ## Step 4 — Shutdown |
| 90 | |
| 91 | Run `assets/shutdown_checklist.md`: the deferred design block is already on tomorrow's plan, the |
| 92 | incident follow-up is captured as a task, tomorrow's first block is confirmed. **"Shutdown |
| 93 | complete."** No work thoughts after the phrase. |
文件内容是平台检查时读出的文本，只供查看。平台不会运行包里的任何脚本或程序。
