Deep Work Session Planner
Designs personalized deep work sessions, break rhythms, and focus protocols to maximize concentration and minimize mental fatigue.
// prompt
You are a focus and deep work specialist who designs personalized concentration systems grounded in cognitive science (attention residue, ultradian rhythms, the Pomodoro technique). Your goal is to engineer deep work sessions that maximize output quality while minimizing mental fatigue.
## My Context
- **Work Type:** {{work_type}}
- **Primary Goal This Week:** {{main_objective}}
- **Typical Energy Pattern:** {{energy_pattern_eg_sharp_mornings_afternoon_slump}}
- **Available Focus Window:** {{hours_per_day}}
- **Biggest Distraction:** {{main_distraction_source}}
- **Work Environment:** {{workspace_description}}
## Design My Deep Work System
**1. Session Architecture**
Recommend an optimal session length and structure matched to my attention span and energy pattern. Justify the choice (e.g. 90-minute ultradian blocks vs. Pomodoro cycles) in one line.
**2. Pre-Work Ritual**
Give a concise 3-5 step warm-up that primes focus and signals "deep work mode" to my brain.
**3. Environmental Setup**
Specify concrete adjustments to my workspace, devices, and notifications to eliminate friction and protect attention.
**4. Distraction Protocol**
Provide if-then rules for handling internal urges and external interruptions without breaking flow.
**5. Break & Recovery Plan**
Schedule breaks with specific recovery activities that restore focus rather than fragment it.
**6. Sample Daily Schedule**
Lay out one realistic day balancing deep work blocks with shallow tasks, meals, and rest.
## Output Format
- Use clear headings and short bullet lists.
- For each session, state **Objective**, **Success Criteria**, and **Focus Tactic**.
- End with 3 **Focus Metrics** I can track daily (e.g. deep minutes logged, interruption count, session rating) and a one-line weekly review prompt.
Keep advice specific, actionable, and tailored to my {{work_type}} — no generic productivity platitudes. Ask me one clarifying question first if any context above is missing.
Fill in the variables
Example run
Generated by Claude Opus 5.5 on September 23, 2026
Inputs used
- Work type
- Backend software engineer (Python/Go microservices, fintech payments team)
- Main objective
- Finish migrating the payment-reconciliation service from a monolith to an event-driven microservice, including writing integration tests, before Friday's sprint review
- Energy pattern, e.g. sharp mornings, afternoon slump
- Sharp and clear-headed from 7:30-11:30am, noticeable energy dip 1:30-3pm after lunch, mild second wind 4-6pm
- Hours per day
- About 5 hours of realistic uninterrupted focus time per day (typically 8am-1pm), remaining hours eaten by standups, code reviews, and Slack
- Main distraction source
- Slack notifications and the compulsion to check the #payments-incidents channel every few minutes, plus context-switching when teammates DM with "quick questions"
- Workspace description
- I work from a home office spare bedroom converted into a desk setup: a standing desk, 27" monitor connected to a work laptop, mechanical keyboard, noise-cancelling headphones. Door doesn't fully block sound, so I sometimes hear my partner on calls in the next room or the dog barking downstairs. I use Slack, Linear for tickets, and a dual-monitor setup (laptop screen + external monitor) where I tend to keep Slack open on the laptop screen at all times "just in case." Phone sits face-up next to keyboard with notifications on. I have a whiteboard on the wall I rarely use. Coffee machine is in the kitchen, a 30-second walk away.
Deep Work System: Payment-Reconciliation Migration Sprint
One clarifying question: Are you on the on-call rotation this week, or is checking #payments-incidents a habit rather than a duty?
I've assumed you're not primary on-call, so the pager covers incidents and the channel can wait. If you are on-call, see the ⚠️ variants marked below. They let you stay reachable without keeping the channel open.
Timeline note: Today is Wednesday. You have about 2.5 focus mornings before Friday's review, so this system is built around that.
1. Session Architecture
Structure: two 90-minute blocks plus one 60-minute block, all in your morning peak.
- Why not Pomodoro: Migration work means holding event schemas, idempotency rules and ledger state in your head at once. Rebuilding that every 25 minutes costs more than the break gives back.
- Block 1 (8:00–9:30): Your hardest, most novel reasoning.
- Block 2 (9:50–11:20): Complex but more structured work.
- Block 3 (11:35–12:35): Mechanical work, because your energy fades after 11:30.
- 4:00–5:30 (optional): A lighter deep session using your second wind.
Wed–Fri roadmap:
| Day | Morning focus | Done when |
|---|---|---|
| Wed | Consumer logic, idempotency, dead-letter handling | Consumer processes events end-to-end locally |
| Thu | Integration tests (testcontainers, Kafka/NATS, DB) | Happy path, duplicate event, out-of-order and poison-message tests are green |
| Fri | Shadow-run comparison (monolith vs. service output), PR polish, demo script | Diff report shows zero reconciliation mismatches on sample data |
2. Pre-Work Ritual (7:45–8:00)
- Phone out of the room. Put it in a drawer or another room, not face-down on the desk. Having it visible drains attention even when silent.
- Quit Slack completely (⌘Q, not minimize). First set your status: "🎧 Deep work until 9:30. DMs answered at 9:30 / 11:20. Urgent → page me."
- Whiteboard the session. Write the objective in one line. Sketch the event flow for today's slice, for example
monolith → outbox → topic → consumer → recon store → DLQ. This loads the mental model before you touch code. - Warm-start the machine. Run
docker compose upand the test suite before the timer starts. You begin from a known state, and slow startup never gives you an excuse to open Slack. - Headphones on, same audio every time (brown noise or one fixed playlist). Start a visible timer. The repeated cue trains your brain to switch into focus mode.
Shutdown ritual (end of each day): Leave one failing test or a // NEXT: comment where you stopped. This limits leftover rumination tonight and gives you an instant entry point tomorrow.
3. Environmental Setup
Screens
- Laptop screen: Stop using it for Slack. Use it for the terminal, test output, logs, or Go/Python docs.
- External monitor: IDE only.
- Browser: Create a separate "Deep Work" profile with no Slack, email or Linear board tabs. Keep only the single Linear ticket open.
Notifications
- Slack (for check-in windows): Set every channel, including #payments-incidents, to mentions only. Mute non-essential channels outright.
- IDE and OS: Turn on Do Not Disturb. Disable Git and Linear popups.
- ⚠️ If on-call: Let PagerDuty/Opsgenie break through Focus mode on your phone. Keep the phone across the room, face-down, with only the pager allowed. The pager is your safety net, so the channel doesn't need your eyes.
Sound
- Wear noise-cancelling headphones with brown noise to mask your partner's calls.
- Agree on a simple door signal with your partner, such as headphones on the handle meaning "in a block."
- Ask for their meeting schedule the night before so you can put mechanical work in noisy slots.
Physical
- Brew a full thermos before 8:00. Save kitchen trips for breaks, where the walk is useful recovery.
- Standing desk: Sit for Block 1 (deep reasoning). Stand for Block 3 and afternoon code reviews. Switch positions only at breaks.
- Whiteboard: Put it to work. Use it for the session objective, a "parking lot" for stray thoughts, and a tally of interruptions.
4. Distraction Protocol
| If… | Then… |
|---|---|
| You feel the urge to check #payments-incidents | Add a tally mark on the whiteboard and say "the pager has it." Check at the next break. |
| A teammate DMs a "quick question" (seen at a check-in) | Reply with: "In a focus block. I'll get to this at 11:20. If it's blocking prod, page me." Batch all answers into the triage window. |
| A build or integration test takes 2–5 minutes | This is your biggest trap. Look at the whiteboard and write your next hypothesis or next test case. Never alt-tab to Slack. |
| You notice an unrelated refactor or tech debt | Add a // TODO(later): comment or a line in scratch.md. Don't touch it. |
| You're stuck for more than 15 minutes on one bug | Write the problem on the whiteboard as if explaining it to a teammate. If still stuck after 10 more minutes, write a precise question to send at the next check-in. |
| Your partner's call or the dog breaks through the headphones | Turn up the brown noise. If it continues past 5 minutes, take your break early and restart the timer. |
| A real incident page arrives | Spend 30 seconds writing a parking note (was doing X, next step Y), then drop everything. The note makes re-entry much faster. |
| You feel an urge to check your phone | It's in another room. That's the whole point. |
5. Break & Recovery Plan
| When | Length | Activity | Avoid |
|---|---|---|---|
| 9:30 | 20 min | 10 min of Slack/DM triage, then 10 min of movement: coffee walk, stairs, look out a window at something far away | Doing triage last, which carries its leftover thoughts into Block 2 |
| 11:20 | 15 min | Second Slack sweep (5 min), then stretch, refill water, stand for Block 3 | Reading #payments-incidents history |
| 12:35–1:30 | Lunch | Away from the desk, walk the dog, no screen | Eating at the desk while "just checking PRs" |
| ~2:15 | 10–15 min | Non-sleep deep rest (a guided relaxation audio) or a short outdoor walk, to soften the post-lunch dip | Caffeine after 2pm, which will hurt tomorrow's peak |
If standup falls mid-morning, treat it as one of your breaks and move the triage window to follow it.
6. Sample Day (Wednesday)
7:45–8:00: Ritual
8:00–9:30: Deep Block 1
- Objective: Build the reconciliation event consumer with idempotent processing (dedupe by event ID, transactional write to the reconciliation store).
- Success Criteria: The consumer processes a replayed batch locally, duplicate events produce no double-writes, and failures route to the DLQ.
- Focus Tactic: Whiteboard the state machine first, then code against it. Sit down, keep only the IDE and terminal open.
9:30–9:50: Triage + movement break
9:50–11:20: Deep Block 2
- Objective: Handle ordering and failure edge cases: out-of-order events, partial ledger matches, retry and backoff.
- Success Criteria: Each edge case has a unit test, and all pass.
- Focus Tactic: Write tests first. Each red→green cycle is a small win that keeps you engaged, and test runs become thinking time, not Slack time.
11:20–11:35: Slack sweep + stretch
11:35–12:35: Deep Block 3 (lighter)
- Objective: Mechanical work: config wiring, structured logging, metrics (processed/failed/DLQ counters), Helm or deploy manifests.
- Success Criteria: The service boots in the local stack with metrics exposed, and the work is committed.
- Focus Tactic: Stand up and work from a checklist. You need less creativity here, so energy matters less.
12:35–1:30: Lunch + dog walk
1:30–3:00: Shallow work (energy dip)
- Code reviews, Slack replies, updating Linear tickets, meetings.
- Take the rest break around 2:15.
3:00–4:00: Collaborative/shallow
- Pair on questions, sync with the team that owns the monolith on cutover or shadow-run plans.
4:00–5:30: Second-wind session
- Objective: Draft the integration test scaffolding for Thursday: testcontainers setup, fixtures, sample payment data.
- Success Criteria: One end-to-end test runs, even if it fails.
- Focus Tactic: Slack closed again for this 90 minutes. Aim for momentum, not perfection.
5:30: Shutdown ritual
- Leave a
// NEXT:marker, write tomorrow's Block 1 objective on the whiteboard, log your metrics.
Focus Metrics (log daily, takes 1 minute)
- Deep minutes logged: Target 240 or more per day. Count only uninterrupted time with Slack closed.
- Self-initiated checks: Count the whiteboard tally marks for Slack, incident-channel and phone urges. Aim for a downward trend by Friday.
- Session output score (1–5): Did you hit the stated success criteria? Pair the score with one word describing the blocker, if any.
Weekly review prompt (Friday afternoon):
"Which block produced my best code this week, what conditions made it work, and what one interruption pattern will I design out next week?"
Related prompts
Personal Development & Hobbies
Confidence & Self-Esteem Builder
Acts as an evidence-based confidence coach building authentic self-esteem through strengths, reframing, graded challenges, and resilience tools.
Personal Development & Hobbies
Daily Reflection & Growth Partner
Acts as a structured daily, weekly, monthly, and quarterly reflection coach building self-awareness and continuous-improvement habits.
Personal Development & Hobbies
Habit Architecture Designer
Designs a science-based, personalized 30-day plan to build positive habits and break negative ones.
Personal Development & Hobbies
Language Learning Conversation Partner
Native-level tutor runs natural target-language conversations with gentle corrections, new vocabulary, and cultural insights.