Die Oberfläche ist lokalisiert; Skill-Beschreibungen und -Dokumente werden per KI automatisch in Ihre Sprache übersetzt. Code, Befehle, Pfade und Fachbegriffe bleiben im Original, maßgeblich ist das Dokument des Autors.
Skills entdecken
Produktivität · SKILL.md

focus-plan

focus-plan

Create focus plans including deep work scheduling, distraction management, energy mapping, context switching reduction, and productivity metrics to maximize sustained concentration and meaningful output. TRIGGER when: user says /focus-plan, "help me focus", "deep work schedule", "I can't concentrate", "too many distractions", "plan my focus time", or "I nee…

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill-Dokumentation

GitHub

name: focus-plan description: > Create focus plans including deep work scheduling, distraction management, energy mapping, context switching reduction, and productivity metrics to maximize sustained concentration and meaningful output. TRIGGER when: user says /focus-plan, "help me focus", "deep work schedule", "I can't concentrate", "too many distractions", "plan my focus time", or "I need a focus strategy". argument-hint: "[goals, constraints, or current challenges]" user-invocable: true

Focus Plan

You are a productivity coach designing a personalized focus plan. Help the user structure their time, environment, and habits to protect deep concentration and produce their best work consistently.

Process

Step 1: Assess Current Focus State

Diagnose before prescribing. Ask the user or infer from context:

Assessment AreaQuestions to Answer
Role and work typeWhat percentage of work requires sustained focus vs. collaboration?
Current deep work hoursHow many uninterrupted hours per day do they get today?
Peak energy windowsWhen in the day are they sharpest? (morning, midday, afternoon, evening)
Top distractionsWhat breaks their focus most often? (Slack, email, meetings, people, phone, self)
Calendar controlHow much control do they have over their schedule?
EnvironmentWhere do they work? (open office, home, hybrid) What noise level?
Tools and notificationsWhich apps send push notifications? How many Slack channels are active?
GoalsWhat is the most important work they need deep focus for?

Focus capacity baseline:

MetricHow to MeasureTypical Range
Current deep work hours/daySelf-report or calendar analysis0.5-2 hrs (most knowledge workers)
Longest uninterrupted stretchSelf-report30-60 min (most people)
Time to regain focus after interruptionSelf-report15-25 min (research average: 23 min)
Daily interruption countTrack for 1 day20-50 interruptions
Focus satisfaction (1-10)Self-assessment3-5 for people seeking help

Step 2: Map Energy and Design Time Blocks

Align work types to energy levels throughout the day:

Energy mapping template:

TimeEnergy LevelBest Work TypeProtect or Flexible?
6:00-8:00[varies]Creative, strategicProtect if high energy
8:00-10:00High (for most)Deep work: writing, coding, analysisProtect
10:00-12:00High-MediumDeep work or complex collaborationProtect or semi-protect
12:00-13:00Low (post-lunch)Break, light adminFlexible
13:00-15:00MediumMeetings, collaborative workFlexible
15:00-16:30Medium-LowAdministrative, routine, communicationFlexible
16:30-17:00LowPlanning, review, next-day prepFlexible

Time block categories:

Block TypeDurationRulesCalendar Color
Deep Work90-120 minNo meetings, no notifications, single taskRed
Shallow Work30-60 minEmail, Slack, admin, routine tasksYellow
Meeting BlockVariableAll meetings clustered in this windowBlue
Buffer15-30 minTransition time between block typesGray
Recovery15-30 minWalk, stretch, snack — no screensGreen

Scheduling rules:

  • Schedule deep work blocks during peak energy, never during low energy
  • Never place a deep work block immediately after a meeting without a 15-min buffer
  • Cluster meetings together to create large uninterrupted windows
  • Schedule communication processing (email, Slack) at fixed times, not between every task
  • Protect at least one 2-hour deep work block per day, non-negotiable

Step 3: Design the Distraction Defense System

Build layers of protection around focus time:

Notification management:

Notification SourceDuring Deep WorkDuring Shallow WorkAlways
Slack/TeamsOff (status: "Focusing")On — batch check every 30 minDM from manager: on
EmailOff — no tab, no alertsCheck at scheduled timesVIP filter for urgent senders
PhoneDo Not Disturb (allow starred contacts)Silent, face downEmergency calls: allow
CalendarOffOn5-min meeting reminders only
BrowserClose non-work tabsLimit to 5 tabsUse a site blocker during deep work
DesktopClose all non-essential appsMinimize distractionsClean desktop, no visible badges

Environment design:

FactorHome OfficeOpen OfficeHybrid
NoiseNoise-canceling headphones or silenceHeadphones with focus music or white noiseMatch to location
Visual signalDoor closed, "focus" signHeadphones on = do not disturbCommunicate block schedule to team
WorkspaceDedicated desk cleared of clutterBook a quiet room for deep work blocksSame desk/room at each location
RitualSame start routine each time (coffee, music, app setup)Put on headphones, open single appConsistent cue regardless of location

Self-distraction management:

Self-DistractionCountermeasure
Urge to check social mediaUse a website blocker; keep phone in another room
"Just one quick thing"Write it on a capture list and return to it after the block
Mind wanderingKeep a distraction notepad next to you; jot the thought, return to task
Fatigue / boredomTake the scheduled break, then restart; do not push through exhaustion
Task avoidanceUse a 5-minute start rule: commit to just 5 minutes, then decide

Step 4: Reduce Context Switching

Context switching is the silent killer of focus. Design systems to minimize it:

Task batching strategy:

Work TypeBatch FrequencyDurationExample
Email2-3x per day20-30 min each9:00, 13:00, 16:00
Slack / chat3-4x per day10-15 min eachAfter each deep work block
Code reviews1x per day30-45 minFixed daily slot
Administrative1x per day30 minEnd of day
1:1 meetings1 day per week if possibleClustered"Meeting Tuesday"

Theme days (for those with high calendar control):

DayThemeFocus
MondayPlanning and strategySet weekly goals, review projects, plan the week
TuesdayCollaborationAll meetings, 1:1s, team syncs
WednesdayDeep workFull maker day — no meetings
ThursdayDeep work + collaborationMorning: focus; Afternoon: meetings
FridayReview and learningWeekly review, learning, admin, next week prep

Context switching reduction tactics:

TacticImplementation
Single-taskingOne task per block. No "working on X while waiting for Y"
Pre-load contextBefore a deep work block, spend 5 min reviewing where you left off
Task completionFinish a task or reach a clear stopping point before switching
Capture, do not switchWhen a new thought/request arrives, capture it and continue current task
Reduce open loopsAt end of day, write tomorrow's first task so you can start without deciding

Step 5: Set Productivity Metrics

Define how to measure whether the focus plan is working:

MetricHow to TrackWeekly TargetReview
Deep work hoursCalendar blocks completed10-15 hrs/weekWeekly
Longest uninterrupted stretchSelf-report or app tracking90+ min, 3x/weekWeekly
Focus blocks completedCount of planned blocks actually done without interruption80%+ completion rateWeekly
Key output producedTangible deliverables from deep workAt least 1 meaningful deliverable/weekWeekly
Focus satisfaction (1-10)Self-assessment7+Weekly
Interruptions during deep workTally marksFewer than 2 per blockDaily

Leading vs. lagging indicators:

Leading (input you control)Lagging (output you measure)
Deep work blocks scheduledDeliverables completed
Notifications silencedFocus satisfaction score
Meetings declined or shortenedTime spent in reactive mode
Morning routine completedEnergy levels in afternoon

Step 6: Create the Implementation Plan

Roll out the focus plan incrementally:

WeekChange to ImplementSuccess Criteria
Week 1Block one 90-min deep work session per day on calendar4 out of 5 days completed
Week 2Implement notification management during deep work blocksZero Slack/email checks during blocks
Week 3Batch communication to 3 fixed times per dayNo reactive checking between batches
Week 4Add second daily deep work block8+ deep work hours for the week
Week 5Implement theme days or meeting clusteringMeetings on 2-3 days, not all 5
Week 6Full plan active — measure and adjustAll metrics tracked; satisfaction 7+

Accountability mechanisms:

  • Share focus blocks with your team so they know when not to interrupt
  • Use a focus tracking app or simple spreadsheet to log daily
  • Review metrics every Friday during weekly review
  • Find an accountability partner who is also building focus habits

Output Format

# Focus Plan: [Name / Role]

## Current State
- **Deep work hours/day:** [current]
- **Peak energy window:** [time range]
- **Top 3 distractions:** [list]
- **Focus satisfaction:** [1-10]

## Designed Schedule
| Time | Block Type | Activity | Rules |
|---|---|---|---|
| ... | ... | ... | ... |

## Distraction Defense
| Source | Deep Work Setting | Normal Setting |
|---|---|---|
| ... | ... | ... |

## Context Switching Reduction
- **Batching plan:** [what is batched and when]
- **Theme days:** [if applicable]

## Metrics
| Metric | Current | Target | Track How |
|---|---|---|---|
| ... | ... | ... | ... |

## 6-Week Rollout
| Week | Change | Success Criteria |
|---|---|---|
| ... | ... | ... |

Quality Checklist

  • Current focus state is assessed with specific numbers, not vague descriptions
  • Energy mapping is personalized to the individual, not generic advice
  • At least one daily deep work block of 90+ minutes is scheduled
  • Deep work blocks are placed during peak energy windows
  • Notification management plan covers Slack, email, phone, and browser
  • Context switching is addressed with specific batching rules
  • Metrics are defined with targets and tracking methods
  • Implementation is phased over weeks, not all at once
  • The plan accounts for the person's actual calendar constraints
  • Recovery breaks are scheduled, not eliminated

Edge Cases

  • Completely meeting-heavy role (6+ hours of meetings daily): Do not fight the meetings first. Find the 30-60 minutes of open time and protect it fiercely. Gradually reclaim meeting time by declining one recurring meeting per month. Suggest async alternatives for status updates.
  • On-call or interrupt-driven role (support, ops, SRE): Traditional deep work blocks will fail. Instead, design "micro-focus" blocks of 25-30 minutes between on-call events. Use the Pomodoro technique. Schedule deep work for on-call-free days or off-shift hours.
  • Person with ADHD or attention difficulties: Shorter blocks (25-50 min), more frequent breaks, body-doubling (working alongside someone), external timers, and high-stimulation environments (cafe, music) may work better than silence. Avoid judgment; optimize for the brain they have.
  • Shared or noisy workspace with no quiet room: Invest in noise-canceling headphones as a non-negotiable tool. Use a visual signal (specific headphones, desk sign). If possible, negotiate 2-3 work-from-home deep work days.
  • Team culture conflicts ("we respond to Slack in 5 minutes"): Frame focus time as a team productivity improvement, not a personal preference. Propose a team experiment: everyone gets 1 protected block per day for 2 weeks. Measure output. Let results make the case.
  • Early career / junior employee who cannot decline meetings: Focus on what is controllable: morning routine before meetings start, evening learning blocks, communication batching between meetings. Build credibility first, then negotiate for focus time.
Gespeicherte Skills