Protect the maker. Score the meetings. Reclaim the time.

references/branding.md

1. Logo
2. Origin quote
3. Workflow diagram
4. Key concepts

Let's audit your calendar right now. No setup needed.

Take a screenshot of your calendar for this week (the week view works best)
and paste it here.

This is a fast first pass — we can set up automated calendar access afterwards
so future audits are hands-free.

1. Extract events from the screenshot using vision — for each event capture: day, time, title, duration
2. Calculate totals — meeting hours, focus hours, contiguous blocks, per-day breakdown (see Regular Flow Step 1a for formulas)
3. Score every meeting using the 5-Dimension framework as default (no framework choice yet — that comes in setup). See

   references/frameworks.md

   for scoring rules.
4. Present the full audit in the standard output format (Red/Orange/Yellow/Green zones with suggestions — see Regular Flow Step 3 output format)
5. Show the gap: current vs target

Here's your audit. Take a look at the scores.

Anything look wrong? Correct any scores and I'll regenerate suggestions.
For example: "Abdul 1:1 should be Green not Yellow" or "Sales standup
score is right but I need to keep it for political reasons"

• Update scores
• Record overrides with reasons
• Regenerate the zone tables and suggestions
• Repeat until user is satisfied

Great — that's your first audit done.

Let's set up so next time is automated. I'll ask a few quick questions
to save your preferences.

1. What should I call you?

2. What's your role? (e.g. CTO, Engineering Manager, IC)

3. How many direct reports? (helps score 1:1s correctly)

4. Top 3 priorities that need deep work this quarter?

5. How should I access your calendar going forward?

   Zero setup (you provide data each time):
   a) Screenshot — paste an image each week
   b) Copy-paste — paste your schedule as text
   c) ICS file — export from any calendar app

   Automated (one-time setup, then hands-free):
   d) Google Calendar MCP [recommended for Google users]
   e) Apple Calendar MCP [recommended for macOS]
   f) icalBuddy [macOS CLI]
   g) gcalcli [Google Calendar CLI]

   See references/calendar-setup.md for setup instructions.

6. Which decision framework do you prefer?

   a) 5-Dimension [default] — what we just used. Scores 5 factors. Most comprehensive.
   b) Eisenhower — simple Urgent vs Important grid. Fastest.
   c) RACI — classifies your role (Accountable/Responsible/Consulted/Informed). Best for cutting meetings where you're just "Informed".
   d) Value vs Effort — scores value generated vs time invested.
   e) Custom — define your own dimensions and scoring.

   See references/frameworks.md for details on each.

• role: "Engineering Leader"
• focus_ratio: value from Step 2 (default 60)
• calendar.tool: "screenshot"
• framework.name: "5-dimension"
• maker_days: ["Tuesday", "Thursday"]

references/frameworks.md

.claude/calendar-audit.md

references/config-guide.md

.claude/modules/meeting-scores.md

You're all set. Run /calendar-audit anytime — ideally Monday mornings.

Your config: .claude/calendar-audit.md
Meeting history: .claude/modules/meeting-scores.md

1. Gather context (calendar, goals, config)
2. Calculate deep work budget and gap
3. Score every meeting using configured framework
4. Present audit with specific suggestions
5. User reviews and overrides
6. Save decisions to meeting memory

calendar.tool

google-calendar-mcp

list-events

apple-calendar-mcp

icalbuddy

icalBuddy -f "" -nc -nrd -df "%Y-%m-%d" -tf "%H:%M" eventsFrom:today to:+5d

gcalcli

gcalcli agenda "$(date +%Y-%m-%d)" "$(date -v+5d +%Y-%m-%d)" --details all --tsv

ics-file

calendar.ics_path

screenshot

copy-paste

manual

• If invoked on a weekend or late Friday, pull next week instead
• Calculate:
  • Total meeting hours (raw duration of all meetings)
  • Effective meeting cost (raw hours + 15 min context-switch per meeting)
  • Total focus hours (remaining time after effective meeting cost)
  • Contiguous focus blocks (2+ hours uninterrupted by meetings)
  • Per-day breakdown (meetings vs focus per day)
• Flag:
  • Days without a contiguous focus block of at least

    min_daily_focus

    hours (default 4)
  • Days with 5+ meetings
  • Back-to-back meetings without breaks
  • Scheduling conflicts (overlapping events)

• User config (

  .claude/calendar-audit.md

  ) for role, priorities, preferences
• Weekly note (if exists) for this week's tasks — estimate deep work hours needed
• Monthly goals (if exists) for north star priorities
• Meeting memory (

  .claude/modules/meeting-scores.md

  ) for previous scores and overrides

Deep Work Budget
────────────────
Work week:              [work_hours, default 40]h
Target focus ratio:     [focus_ratio, default 60]%
Target focus hours:     [work_hours * ratio]h
Target meeting hours:   [work_hours * (1-ratio)]h
Min daily focus block:  [min_daily_focus, default 4]h contiguous

Current meetings:       Xh (raw) / Yh (with transitions)
Current focus:          Zh
Current ratio:          Z/work_hours = N%

Gap:                    [target - current]h to reclaim

• Every day must have at least one contiguous block of

  min_daily_focus

  hours (default 4h) — scattered focus doesn't count
• No day with zero focus time
• At least 1 "maker day" (4+ contiguous hours focus) per week

1. Ask user to confirm, override, or adjust any scores
2. For overrides, record the reason (e.g. "Keep despite score — important relationship")
3. Save all decisions to meeting memory

• "What would happen if you skipped this for 2 weeks as an experiment?"
• "Could you send a delegate and get a 2-line summary?"

.claude/modules/meeting-scores.md

• Current scores for all meetings (with framework used)
• User overrides and reasons
• Week-over-week comparison
• Running trend (are meetings increasing or decreasing?)

undefined

Running log of meeting audit scores and decisions.

• Contiguous blocks matter more than total hours. 3 hours scattered across 30-min gaps is worth less than 1 contiguous 2-hour block. The target is one 4-hour uninterrupted stretch per day — that's where real work happens.
• Don't just count meetings — count transitions. Each meeting has ~15 min of context-switching cost. A day with 6x30min meetings costs ~4.5h, not 3h.
• Batch meetings on specific days when possible. Aim for 1-2 "maker days" (mostly focus) and 2-3 "manager days" (meetings batched).
• Morning focus is often more valuable than afternoon focus for creative and learning work.
• The goal is not zero meetings — it's the right meetings at the right frequency and duration.
• Meeting load creeps. Without regular audits, meetings accumulate 1-2 per month. This skill is the counterweight.
• Career items are the first to drop when meetings increase. Deep work protection is career protection.

• Cal Newport, Deep Work — Knowledge workers need 3-4h of uninterrupted focus daily for meaningful output
• Paul Graham, Maker's Schedule — Meetings destroy maker productivity disproportionately; a single meeting can ruin a half-day
• Parkinson's Law — Meetings expand to fill the time allotted; default to 25min or 50min
• Context-switching research (Gloria Mark, UC Irvine) — Takes ~23 minutes to fully refocus after an interruption
• Meeting cost formula — A 1h meeting with 8 people costs 8 person-hours + 8x15min context switches = 10h of organisational productivity