focus-timeboxing-8020

$npx mdskill add lyndonkl/claude/focus-timeboxing-8020

Prioritize high-impact work using Pareto principles and timeboxing.

  • Eliminates context-switching by batching tasks and enforcing focus blocks.
  • Integrates with calendar systems to schedule deep work periods.
  • Decides recommendations by identifying vital 20% of tasks.
  • Delivers a structured weekly plan with daily execution checkpoints.

SKILL.md

.github/skills/focus-timeboxing-8020View on GitHub ↗
---
name: focus-timeboxing-8020
description: Combines Pareto prioritization (80/20), timeboxing, and deep work techniques to manage attention, eliminate context-switching, and maximize high-impact output. Use when managing time and attention, combating procrastination, prioritizing high-impact work, planning daily/weekly schedules, or when user mentions timeboxing, Pomodoro, deep work, 80/20 rule, Pareto principle, focus blocks, task batching, or energy management.
---
# Focus, Timeboxing, and 80/20

## Table of Contents
- [Workflow](#workflow)
- [Common Patterns](#common-patterns)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)

## Example

**Scenario**: Engineer overwhelmed with tickets, meetings, code reviews, and a complex feature.

**80/20**: Ship payment feature (biggest customer request, revenue impact) = vital 20%.

**Weekly Plan**:
- Mon-Wed mornings (9-12): Deep work on payment feature (no meetings, Slack off)
- Mon-Wed afternoons: Code reviews, standups, pair programming
- Thu-Fri: Batch meetings, planning, admin, lower-priority tickets

**Outcome**: Feature shipped in 3 days (18 hours deep work) vs. estimated 2+ weeks with constant interruptions.

## Workflow

Copy this checklist and track your progress:

```
Focus & Timeboxing Progress:
- [ ] Step 1: Identify your 80/20
- [ ] Step 2: Design focus blocks
- [ ] Step 3: Timebox your week
- [ ] Step 4: Timebox your day
- [ ] Step 5: Execute with discipline
- [ ] Step 6: Review and adjust
```

**Step 1: Identify your 80/20**

What 20% of tasks drive 80% of your results? Separate vital few from trivial many. See [resources/template.md](resources/template.md#8020-analysis-template).

**Step 2: Design focus blocks**

Block time for deep work on high-impact tasks. Match duration to task type (Pomodoro 25min, Deep Work 90-120min). See [resources/template.md](resources/template.md#focus-block-design-template) and [resources/methodology.md](resources/methodology.md#1-deep-work-and-focus-blocks).

**Step 3: Timebox your week**

Allocate weekly calendar: deep work blocks, meeting blocks, batched admin, buffer time. See [resources/template.md](resources/template.md#weekly-timeboxing-template) and [resources/methodology.md](resources/methodology.md#2-timeboxing-techniques).

**Step 4: Timebox your day**

Break day into time-constrained blocks with start/end times. Schedule breaks. Plan evening hard stop. See [resources/template.md](resources/template.md#daily-timeboxing-template).

**Step 5: Execute with discipline**

Honor timeboxes. Use timers. Eliminate distractions (Slack off, phone away, close tabs). Take breaks. See [resources/methodology.md](resources/methodology.md#3-execution-discipline).

**Step 6: Review and adjust**

Weekly review: Did you protect deep work? What interrupted focus? Adjust schedule. See [resources/template.md](resources/template.md#weekly-review-template) and [resources/methodology.md](resources/methodology.md#4-energy-management-and-optimization).

Validate using [resources/evaluators/rubric_focus_timeboxing_8020.json](resources/evaluators/rubric_focus_timeboxing_8020.json). **Minimum standard**: Average score ≥ 3.5.

## Common Patterns

**Pattern 1: Pomodoro Technique (25 min focus)**
- **Format**: 25 min focused work + 5 min break, repeat 4×, then 15-30 min break
- **Best for**: Tasks with high resistance (procrastination), need for frequent breaks, building focus habit
- **Tools**: Timer, task list, distraction blockers
- **When**: Short tasks, starting new habits, high-distraction environments
- **Guardrails**: Don't interrupt Pomodoro mid-session, actually take breaks (don't skip)

**Pattern 2: Deep Work Blocks (90-120 min)**
- **Format**: 90-120 min uninterrupted focus on single cognitively demanding task
- **Best for**: Complex thinking (writing, coding, design, strategy), high-value creative work
- **Preparation**: Clear goal for session, all resources ready, distractions eliminated
- **When**: Peak energy hours (usually morning), maximum 2-3 blocks per day
- **Guardrails**: No meetings during deep work, Slack/email off, phone in another room

**Pattern 3: Weekly 80/20 Planning**
- **Format**: Sunday/Monday - identify top 3 high-impact goals for week, schedule deep work blocks
- **Best for**: Strategic prioritization, ensuring vital few get attention
- **Output**: 3-5 focus blocks (90-120 min each) on calendar for week's top priorities
- **When**: Start of week, quarterly planning, project kickoffs
- **Guardrails**: Protect these blocks ruthlessly, treat like unmovable meetings

**Pattern 4: Task Batching (30-60 min blocks)**
- **Format**: Group similar low-cognitive-load tasks (emails, calls, admin) into single session
- **Best for**: Reducing context-switching, clearing small tasks efficiently
- **Examples**: Email batches (11am, 4pm), meeting blocks (Tue/Thu afternoons), admin Fridays
- **When**: Low-energy periods, after deep work, end of day
- **Guardrails**: Set timer, don't let batches expand, resist checking email outside batches

**Pattern 5: Maker's Schedule (Half-day or Full-day blocks)**
- **Format**: Uninterrupted half-days (4+ hours) or full days for creative/technical work
- **Best for**: Large projects (research paper, product launch, complex feature), flow-state work
- **Preparation**: Clear all meetings for that period, OOO on Slack, backup plan if interrupted
- **When**: Critical deadlines, breakthrough work needed, once/week minimum for makers
- **Guardrails**: Communicate boundaries, delegate urgent issues, plan breaks within block

**Pattern 6: Energy-Based Scheduling**
- **Format**: Match task type to energy level (peak → deep work, trough → admin, recovery → meetings)
- **Best for**: Maximizing output while preventing burnout
- **Typical cycle**: Peak (9am-12pm) → Trough (2-3pm) → Recovery (4-5pm)
- **When**: Designing weekly/daily schedules, recovering from overwork
- **Guardrails**: Track your actual energy patterns (not generic), honor low-energy periods with rest

## Guardrails

1. **Protect deep work time**: No meetings, no Slack, no email during focus blocks. One interruption destroys 20+ minutes of flow. Schedule deep work during peak energy (usually mornings).

2. **Use Parkinson's Law**: Work expands to fill available time. Shorter timeboxes force prioritization and prevent perfectionism. A 90-minute timebox with a clear outcome beats open-ended "work on this."

3. **Identify the 80/20**: Force rank tasks by impact. The top 20% should get 80% of focus time. Cut, delegate, or batch the rest.

4. **Energy matters more than time**: 8 hours tired produces less than 4 hours energized. Match intensity to energy level. Troughs are for admin and meetings, not complex thinking.

5. **Build in buffer**: Leave ~20% unscheduled for unexpected issues, overflow, and breaks. Over-scheduling is fragile; one delay cascades.

6. **Set hard stops**: Define an end-of-day time. Constrained time forces prioritization; endless time enables procrastination.

7. **Take breaks**: After 90 minutes of deep work, take 10-15 minutes. Walk, stretch, look outside. Focus degrades after 90-120 minutes without a break.

8. **Measure focus quality, not hours**: 3 hours of deep work outperforms 8 hours of distracted work. Track completed focus blocks per week, not total hours.

**Common pitfalls:**

- ❌ **No real deep work blocks**: Calendar full of meetings, "focus time" constantly interrupted. Protect minimum 2-3× 90-min blocks per week.
- ❌ **Ignoring 80/20**: Everything feels important. Force rank. If you can't identify top 20%, ask: "If I could only work 10 hours this week, what would I do?"
- ❌ **Timeboxing trivia**: Scheduling every email, every Slack message. Batch low-value tasks, don't timebox them individually.
- ❌ **Skipping breaks**: "I'll break after I finish this." Then work 4 hours straight, output quality tanks. Use timer, force breaks.
- ❌ **Peak hours on admin**: Checking email at 9am (peak energy). Save admin for afternoon trough. Peak hours = deep work only.
- ❌ **Overcommitting**: Timeboxing 10 hours of work into 8-hour day. Be realistic. Under-schedule, over-deliver.

## Quick Reference

**Timeboxing durations:**

| Duration | Best For | Rest After |
|----------|----------|------------|
| **25 min** | Pomodoro, high-resistance tasks, building habit | 5 min |
| **50 min** | Focused work, moderate complexity | 10 min |
| **90 min** | Deep work, complex thinking, creative tasks | 15 min |
| **120 min** | Maximum deep work (rare, high expertise) | 20-30 min |
| **Half-day (4h)** | Maker's schedule, breakthroughs, flow state | Lunch + afternoon off |

**Energy-based scheduling:**

| Time | Energy Level | Task Type | Examples |
|------|--------------|-----------|----------|
| **6-9am** | Peak (early risers) | Deep work | Writing, coding, strategy |
| **9am-12pm** | Peak (most people) | Deep work | Complex problems, creative work |
| **12-2pm** | Lunch dip | Meetings, social | Standups, 1:1s, collaboration |
| **2-3pm** | Trough | Admin, batching | Email, Slack, expense reports |
| **3-5pm** | Recovery | Moderate work | Code reviews, planning, lighter tasks |
| **Evening** | Low | Rest or routine | Reading, exercise, NOT deep work |

**80/20 identification:**

Ask these questions:
- "If I could only work 10 hours this week, what would I do?"
- "Which tasks, if done well, make everything else easier or unnecessary?"
- "What creates 10× value vs. 1× value?"
- "What will matter in 6 months? What won't?"

**Focus blockers (eliminate during deep work):**

- [ ] Slack/Teams (quit app or set DND)
- [ ] Email (close tab/app)
- [ ] Phone (different room, airplane mode)
- [ ] Browser tabs (close all except work-related)
- [ ] Open floor plans (noise-canceling headphones, office door)
- [ ] Notifications (disable all)
- [ ] Meetings (schedule-free mornings)

**Batching categories:**

- **Email batches**: 11am, 4pm (2× per day max)
- **Meeting blocks**: Tue/Thu afternoons
- **Admin batch**: Friday afternoons (expense reports, timesheets, planning)
- **Code review batch**: After lunch (30-60 min)
- **Quick calls batch**: 30-min slots back-to-back

**Weekly planning template** (simplified):

```
Monday-Wednesday mornings: Deep work on Priority 1 (3× 90-min blocks)
Monday-Wednesday afternoons: Meetings, collaboration, moderate work
Thursday: Deep work on Priority 2 (morning), meetings (afternoon)
Friday: Batched admin, planning next week, code reviews
```

**Inputs required:**
- **Current commitments**: Meetings, recurring tasks, deadlines
- **Energy patterns**: When are you most/least energized? (track for 1 week)
- **Top priorities**: What are your 3-5 most important outcomes this week/month?
- **Task list**: Everything competing for attention (to identify 80/20)

**Outputs produced:**
- `weekly-timeboxed-schedule.md`: Calendar with focus blocks, meeting blocks, batch times
- `daily-plan.md`: Time-blocked day with start/end times, breaks scheduled
- `8020-analysis.md`: Prioritized task list with vital few identified
- `focus-time-tracker.csv`: Log of focus blocks completed, quality, interruptions

More from lyndonkl/claude

SkillDescription
abstraction-concrete-examplesBuilds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
academic-letter-architectGuides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
adr-architectureDocuments significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
adverse-selection-priorProduces a Bayesian prior probability that an offered transaction is +EV for the recipient, given that the counterparty chose to propose it. Applies Akerlof market-for-lemons logic -- if they offered it, they believe it is +EV for them, so the prior that it is +EV for us is materially below 50%. Reusable across trade evaluation, waiver drops (another team dropping a player is also adverse selection), job-offer analysis, M&A, and any "someone offered me this" situation. Use when you receive an unsolicited trade/offer/proposal, analyzing incoming trade prior, evaluating why a counterparty proposed a deal, or when user mentions adverse selection, market for lemons, why did they offer this, incoming trade prior, they proposed it, Bayesian adjustment on received offer.
alignment-values-north-starCreates actionable alignment frameworks that give teams a shared North Star (direction), values (guardrails), and decision tenets (behavioral standards). Enables autonomous decision-making while maintaining organizational coherence. Use when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
analogy-weight-checkFor every analogy in a substacker draft, verifies it carries mechanical weight — the analogy does real work explaining the mechanism, not merely decorates it. Cross-references analogy-catalog.md for novelty (is this analogy reused from a prior post?) and domain fit (biology > organizational > sports preferred; physics/military disfavored). Use whenever an analogy appears in the draft. Trigger keywords: analogy weight, decorative, mechanical weight, reused analogy, catalog check, metaphor check.
answer-uncomfortable-questionTakes one strategic question about substacker ("should we launch paid?", "is this section dead?", "are we writing for the wrong audience?") and produces the mandatory evidence + reasoning + downside triad plus a recommendation. Used 3 times per Growth Strategist review. Trigger keywords: uncomfortable question, strategic question, evidence reasoning downside, triad.
attribute-performanceFor each substacker post that materially over- or under-performs the rolling baseline (|z| ≥ 1.0), produces a plain-English attribution paragraph with calibrated confidence (high / medium / low / unexplained). Considers subject-line effect, topic zeitgeist, external share, day-of-week, length effect, and audience-notes signals. Labels unexplained outliers explicitly rather than fabricating a story. Use after compute-baseline when outlier posts exist. Trigger keywords: attribution, why did this post work, outlier explanation, performance analysis.
auction-first-price-shadingComputes the optimal shaded bid for a first-price sealed-bid auction given a true private value, an estimate of the number of competing bidders N, and a value-distribution assumption. Implements the `(N-1)/N` equilibrium shading rule for uniform private values, adjusts for log-normal or empirical value distributions, layers a risk-aversion adjustment, and caps output against the bidder's remaining budget. Domain-neutral auction theory reusable across fantasy sports (baseball FAAB, NBA/NHL waiver auctions), prediction-market limit sizing, sealed procurement bids, and any blind-bid context. Use when user mentions "first-price auction bid", "sealed bid shading", "(N-1)/N", "FAAB bid amount", "auction shading", "optimal bid first-price", "bid for sealed-bid", "blind bid sizing", or when downstream logic needs a principled shade factor rather than an ad-hoc heuristic.
auction-winners-curse-haircutApplies a Bayesian haircut to a bid valuation for common-value auctions where winning is itself evidence the bidder over-estimated. Takes a raw valuation, a value-type classification (common_value / private_value / mixed), the number of informed bidders N, and a signal-dispersion estimate, and returns an adjusted valuation. Domain-neutral and reusable across fantasy FAAB, prediction markets, M&A bids, ad-auction budgets, and any generic bidding context. Use when user mentions "winner's curse", "common value auction", "valuation haircut", "adverse valuation", "Bayesian bid adjustment", or "over-paying in auction".