---
name: focus-time-management
description: Deep work scheduling, time blocking, Pomodoro technique, distraction management, and energy-aware productivity. Use when optimizing focus time, building work schedules, or managing distractions.
domain: productivity
tags: [focus, deep-work, time-blocking, pomodoro, productivity, schedule]
---

## When NOT to Use

- Task is outside your authorization scope
- You need to implement controls (use implementing-* skills)
- Task is about analysis, not action (use analyzing-* skills)
- You don't have access to target systems
- Task requires compliance expertise (consult professionals)
- Task is about defense, not offense (use defensive skills)


## Overview

Evidence-based focus and time management system combining deep work principles, time blocking, and energy-aware scheduling. Helps agents create optimal work schedules that maximize productive output.

## When to Use

- Creating a daily/weekly work schedule
- Optimizing deep focus time for complex tasks
- Managing distractions and context switching
- Planning energy-aware work blocks
- Building sustainable productivity habits

## Process
1. Validate input and check prerequisites
2. Initialize required connections and contexts
3. Execute core operation with monitoring
4. Validate output against expected format
5. Deliver results and log execution summary


### 1. Energy Audit

Map your energy patterns over 2 weeks:

```
Energy Level by Time of Day:
- 6-9 AM:  [high/medium/low]
- 9-12 PM: [high/medium/low]
- 12-2 PM: [high/medium/low]
- 2-5 PM:  [high/medium/low]
- 5-8 PM:  [high/medium/low]
```

### 2. Time Blocking Template

```
[Day] Schedule:

06:00-07:00  Morning routine (no screens)
07:00-09:00  DEEP WORK — [most important task] (high energy)
09:00-09:30  Break + email/messages
09:30-11:30  DEEP WORK — [second priority]
11:30-12:00  Communication block (calls, messages)
12:00-13:00  Lunch + walk (no work)
13:00-14:30  SHALLOW WORK — admin, meetings, emails
14:30-14:45  Break
14:45-16:30  DEEP WORK — [creative/collaborative work]
16:30-17:00  Review + plan tomorrow
17:00+       Off (recovery)
```

### 3. Pomodoro Protocol

Standard Pomodoro:
1. Choose one task
2. Set timer for 25 minutes
3. Work with full focus (no interruptions)
4. 5-minute break
5. After 4 pomodoros: 15-30 minute break

Modified for deep work:
- 50-minute focus blocks with 10-minute breaks
- 90-minute ultradian rhythm blocks with 20-minute breaks

### 4. Distraction Management

**External distractions:**
- Phone: airplane mode during deep work
- Notifications: disable all except emergency contacts
- Open office: noise-canceling headphones or "do not disturb" signal
- Email/Slack: check at scheduled times only (3x/day max)

**Internal distractions:**
- Capture stray thoughts in a "parking lot" notebook
- Return to task immediately after writing the thought
- Practice the "2-minute rule": if it takes < 2 min, do it now; otherwise schedule it

### 5. Weekly Review

Every Friday:
1. Review completed tasks vs. planned
2. Identify top 3 wins
3. Identify top 3 friction points
4. Plan next week's deep work blocks
5. Schedule buffer time (20% of week)

## Focus Techniques

| Technique | Best For | Duration | Break |
|-----------|----------|----------|-------|
| Pomodoro | Routine tasks | 25 min | 5 min |
| Deep Work Block | Complex problems | 90 min | 20 min |
| Time Boxing | Scoping creep | 60 min | 10 min |
| Eat the Frog | Procrastination | First task | — |
| 2-Minute Rule | Small tasks | < 2 min | — |

## Anti-Patterns

- Multitasking = context switching = 40% productivity loss
- No breaks = burnout = diminishing returns after 4 hours
- Open calendar = reactive mode = no deep work
- Perfectionism on shallow tasks = time theft from deep work

## Verification

- [ ] At least 2 hours of deep work scheduled daily
- [ ] Energy audit completed and schedule aligned
- [ ] Distraction management system in place
- [ ] Weekly review conducted every Friday
- [ ] Buffer time (20%) included in weekly schedule

## How to Use

1. Invoke the skill when relevant domain keywords appear in the request
2. Provide required inputs as specified in the skill definition
3. Review the output for correctness before delivering to the user
4. Combine with related skills for complex multi-step workflows