Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Generate an energy-optimized, time-blocked daily plan based on circadian rhythm research and GTD principles
.claude/skills/brianrwagner-plan-my-day/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | 144% | 0% |
| case-14 | ✗→✓ | ▲ Improved | 192% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 229% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 204% | 0% |
| case-22 | ✓→✓ | = Same ✓ | 163% | 0% |
Generate a clean, actionable hour-by-hour plan for the day based on priorities, energy patterns, and constraints.
Detect from context or ask: "Quick priorities, full day plan, or full plan + weekly structure?"
| Mode | What you get | Best for | |------|-------------|----------| | quick | Top 3 priorities + rough time blocks, 2 min | Morning sprint, already know the day | | standard | Full hour-by-hour energy-optimized plan | Default daily planning | | deep | Full plan + energy pattern analysis + weekly structure recommendations | Overhauling your schedule, high-performance week |
Default: standard — use quick if they say "just help me prioritize." Use deep if they want to rethink their week, not just plan today.
Problem with "just asking": You get a different plan each time. No consistency, no memory of what works, no optimization over time.
This skill provides:
You can replicate this by writing the same detailed prompt every day, manually checking your calendar, remembering your energy patterns, and tracking completion rates. Or use this skill in 2 minutes.
/plan-my-day [optional: YYYY-MM-DD for future date]With custom energy profile:
/plan-my-day --peak 9-11,14-16 --recovery 13-14Peak Performance (Morning): 9:00 AM - 12:00 PM
Secondary Peak (Afternoon): 2:00 PM - 4:00 PM
Administrative (Late Afternoon): 4:00 PM - 6:00 PM
Recovery Blocks: 12:00 PM - 1:00 PM, 6:00 PM+
Wind Down (Evening): After 7:00 PM
Ask for each potential priority:
Filter: Pick the 3 with highest impact×urgency score
Sequencing logic:
Buffer rule: Only schedule 80% of available time
markdown# Daily Plan - [Day], [Month] [Date], [Year] ## Today's Mission **Primary Goal:** [One-sentence outcome for the day] **Top 3 Priorities:** 1. [Priority 1 with specific, measurable outcome] 2. [Priority 2 with specific, measurable outcome] 3. [Priority 3 with specific, measurable outcome] **Success looks like:** [What "done" means today] --- ## Time-Blocked Schedule ### 8:00 - 9:00: Morning Prime 🌅 **Focus:** Wake up, coffee, light movement, review plan - [ ] Morning routine (30 min) - [ ] Review today's plan + priorities (10 min) - [ ] Quick inbox scan (15 min - flag only, don't respond) **Energy level:** Building --- ### 9:00 - 11:00: Deep Work Block 1 🎯 [PRIORITY #1] **Focus:** [Specific priority 1 task] - [ ] [Concrete subtask 1] - [ ] [Concrete subtask 2] - [ ] [Concrete subtask 3] **Target:** [Measurable outcome by 11:00] **Protection:** Phone off, Slack paused, door closed --- ### 11:00 - 11:15: Break ☕ **Focus:** Step away from desk - Physical movement (walk, stretch) - Hydrate - No screens --- ### 11:15 - 12:30: Deep Work Block 2 🎯 [PRIORITY #2] **Focus:** [Specific priority 2 task] - [ ] [Concrete subtask 1] - [ ] [Concrete subtask 2] **Target:** [Measurable outcome by 12:30] --- ### 12:30 - 1:30: Lunch Break 🍽️ **Focus:** Eat, recharge, disconnect - Proper meal (not at desk) - 15-minute walk if possible - No work talk **Energy level:** Recovery --- ### 1:30 - 3:00: Focused Work Block 🎯 [PRIORITY #3] **Focus:** [Specific priority 3 task] - [ ] [Concrete subtask 1] - [ ] [Concrete subtask 2] **Target:** [Measurable outcome by 3:00] --- ### 3:00 - 3:15: Break ☕ **Focus:** Recharge --- ### 3:15 - 4:30: Meetings / Collaborative Work 👥 **Focus:** [Meeting name or collaborative task] - [ ] [Meeting 1 with agenda] - [ ] [Follow-up actions from meetings] **Prep:** Review agendas 10 minutes before --- ### 4:30 - 5:30: Admin & Communication 📧 **Focus:** Process inbox, respond to messages, light tasks - [ ] Clear email inbox (respond, archive, defer) - [ ] Slack catch-up and responses - [ ] Update project trackers - [ ] Quick wins / small tasks **Energy level:** Lower (perfect for admin) --- ### 5:30 - 6:00: Planning & Wrap-Up 📋 **Focus:** Close the day, plan tomorrow - [ ] Evening check-in (see below) - [ ] Tomorrow's top 3 priorities draft - [ ] Inbox zero for peace of mind - [ ] Close all work apps --- ### 6:00 PM+: Personal Time 🏡 **No work beyond this point** --- ## Success Criteria ### Must-Have (Non-Negotiable) ✓ - [ ] Priority 1 complete: [Specific outcome] - [ ] Priority 2 complete: [Specific outcome] - [ ] At least 80% progress on Priority 3 ### Should-Have (Important) ⭐ - [ ] [Secondary task 1] - [ ] [Secondary task 2] ### Nice-to-Have (Bonus) 💡 - [ ] [Bonus task 1] - [ ] [Bonus task 2] --- ## Evening Check-In (5 minutes at 5:30 PM) **Completion status:** - Priority 1 done? **YES / NO** - [If no, why?] - Priority 2 done? **YES / NO** - [If no, why?] - Priority 3 done? **YES / NO** - [If no, why?] **What went well:** [What worked today? What helped you execute?] **What got stuck:** [Where did you lose time? What blocked you?] **Energy assessment:** - Peak hours productive? **YES / NO** - Breaks taken? **YES / NO** - Felt energized or drained? **[Score 1-10]** **Tomorrow's adjustment:** [What to change in tomorrow's plan based on today?] --- ## Quick Decision Framework **Before saying YES to anything today:** 1. **Is this one of my top 3 priorities?** - YES → Schedule it in appropriate energy window - NO → Go to #2 2. **Does this directly support today's mission?** - YES → Add to relevant time block - NO → Go to #3 3. **Can this wait until tomorrow?** - YES → Add to tomorrow's list - NO → Question if it's really urgent **If NO to all three → Decline or defer** ---
Context: Product launch week, high-stakes demos, team coordination
markdown## Top 3 Priorities: 1. Finalize launch announcement (900 words, 3 versions) - DONE by 11:30 2. Run partner demo with clear next steps - DONE by 3:00 3. Team sprint planning with Q2 priorities set - DONE by 5:00 ## Schedule: - 9:00-11:30: Deep work → Launch copy (Priority #1) - 12:30-2:45: Partner demo prep + execution (Priority #2) - 3:00-4:45: Sprint planning with team (Priority #3) - 5:00-5:30: Email/admin/wrap ## Evening Check-In: ✓ Priority 1: YES (shipped 3 versions, CEO approved) ✓ Priority 2: YES (partner committed, contract signed) ✓ Priority 3: YES (team aligned, stories pointed) What worked: Protected deep work time for writing, prepped demo thoroughly Tomorrow: Start execution on sprint, less coordination overhead
Context: IC developer, needs 6+ hours of uninterrupted coding
markdown## Top 3 Priorities: 1. Ship authentication refactor (PR ready for review) - DONE by 12:00 2. Debug production issue #847 (root cause found + fix deployed) - DONE by 4:00 3. Documentation for new API endpoints (published) - DONE by 6:00 ## Schedule: - 9:00-12:00: Deep work → Auth refactor (Priority #1) - 1:00-4:00: Deep work → Debug + deploy (Priority #2) - 4:15-5:45: Documentation writing (Priority #3) - 5:45-6:00: Update tickets, close day ## Protections: - Slack: Paused 9am-12pm, 1pm-4pm - No meetings scheduled - Phone: DND mode ## Evening Check-In: ✓ Priority 1: YES (PR approved, merged) ✓ Priority 2: YES (issue resolved, monitoring green) ✓ Priority 3: 90% (docs drafted, needs final review tomorrow) What worked: Zero meetings = maximum flow state Tomorrow: Finish docs, start new feature work
Context: Leadership role, multiple teams, coordination day
markdown## Top 3 Priorities: 1. Align exec team on Q2 budget priorities - DONE by 11:00 2. Resolve team conflict (performance conversation) - DONE by 3:00 3. Approve 3 critical design reviews - DONE by 5:30 ## Schedule: - 8:30-9:00: Pre-meeting prep (agendas, talking points) - 9:00-11:00: Exec budget meeting (Priority #1) - 11:15-12:15: 1-on-1 performance conversation (Priority #2) - 1:30-3:00: Design review meetings (Priority #3, all 3 back-to-back) - 3:15-4:30: Email/admin/follow-ups from meetings - 4:30-5:00: Next week prep + team updates ## Evening Check-In: ✓ Priority 1: YES (budget approved, owners assigned) ✓ Priority 2: YES (performance plan agreed, follow-up scheduled) ✓ Priority 3: YES (2 approved, 1 needs revision) What got stuck: Back-to-back meetings = no thinking time Tomorrow: Block 2-hour deep work window, fewer meetings
User: Marketing manager at B2B SaaS company, struggled with reactive days
Before using skill:
After implementing plan-my-day:
Results after 8 weeks:
Key insight: "The daily plan gave me permission to say no. If it wasn't in my Top 3, I deferred it. That one change unlocked everything."
/plan-my-day/plan-my-day --mode high-output/plan-my-day --mode deep-work/plan-my-day --mode coordinationbash# Copy skill to your skills directory cp -r plan-my-day $HOME/.openclaw/skills/ # Verify installation /plan-my-day --version
No dependencies required - Pure planning logic.
❌ Planning too much - If you schedule 100% of your time, you'll fail. Always leave 20% buffer. ❌ Ignoring energy windows - Putting hard thinking work at 4pm sets you up for failure. ❌ Skipping breaks - 90-minute focus blocks REQUIRE 15-minute breaks or performance drops. ❌ No evening reflection - Without check-ins, you can't improve your planning accuracy. ❌ Changing Top 3 mid-day - Unless genuinely urgent, stick to morning priorities.
A good daily plan has:
Issues or suggestions? Provide:
Built on circadian rhythm research (Roenneberg), deliberate practice principles (Ericsson), and GTD methodology (Allen).
Plan your day in 2 minutes. Execute with focus. Win consistently.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-22 | pass→pass | 14,461 | 15,469 | +7% | 1 | 1 | 0% | 2,847 | 7,500 | +163% | 0 | 0 | — |
case-01 | fail→fail | 12,722 | 12,043 | -5% | 1 | 1 | 0% | 2,079 | 6,443 | +210% | 0 | 0 | — |
case-02 | fail→fail | 12,377 | 13,533 | +9% | 1 | 1 | 0% | 2,136 | 6,734 | +215% | 0 | 0 | — |
case-03 | fail→fail | 14,900 | 14,821 | -1% | 1 | 1 | 0% | 2,535 | 6,942 | +174% | 0 | 0 | — |
case-04 | pass→pass | 10,172 | 11,725 | +15% | 1 | 1 | 0% | 1,665 | 6,318 | +279% | 0 | 0 | — |
case-05 | fail→pass | 15,904 | 7,197 | -55% | 1 | 1 | 0% | 2,245 | 5,479 | +144% | 0 | 0 | — |
case-06 | pass→pass | 16,319 | 11,700 | -28% | 1 | 1 | 0% | 2,483 | 6,207 | +150% | 0 | 0 | — |
case-07 | fail→fail | 15,242 | 13,456 | -12% | 1 | 1 | 0% | 2,241 | 6,486 | +189% | 0 | 0 | — |
case-13 | pass→pass | 9,223 | 8,221 | -11% | 1 | 1 | 0% | 1,511 | 5,727 | +279% | 0 | 0 | — |
case-14 | fail→pass | 13,754 | 12,059 | -12% | 1 | 1 | 0% | 2,119 | 6,185 | +192% | 0 | 0 | — |
case-15 | fail→pass | 13,125 | 9,920 | -24% | 1 | 1 | 0% | 1,869 | 6,144 | +229% | 0 | 0 | — |
case-16 | fail→pass | 11,645 | 8,389 | -28% | 1 | 1 | 0% | 1,863 | 5,660 | +204% | 0 | 0 | — |
case-08 | fail→fail | 6,418 | 4,066 | -37% | 1 | 1 | 0% | 941 | 4,899 | +421% | 0 | 0 | — |
case-09 | fail→fail | 10,183 | 15,602 | +53% | 1 | 1 | 0% | 1,477 | 6,918 | +368% | 0 | 0 | — |
case-10 | fail→fail | 14,288 | 11,688 | -18% | 1 | 1 | 0% | 2,643 | 6,426 | +143% | 0 | 0 | — |
case-11 | fail→fail | 12,165 | 14,299 | +18% | 1 | 1 | 0% | 1,992 | 6,724 | +238% | 0 | 0 | — |
case-12 | fail→fail | 14,881 | 13,469 | -9% | 1 | 1 | 0% | 2,271 | 6,497 | +186% | 0 | 0 | — |
case-17 | pass→pass | 9,084 | 12,281 | +35% | 1 | 1 | 0% | 1,508 | 6,427 | +326% | 0 | 0 | — |
case-18 | pass→pass | 10,752 | 9,127 | -15% | 1 | 1 | 0% | 1,736 | 5,872 | +238% | 0 | 0 | — |
case-19 | pass→pass | 15,844 | 13,559 | -14% | 1 | 1 | 0% | 3,029 | 6,844 | +126% | 0 | 0 | — |
case-20 | pass→pass | 19,042 | 17,061 | -10% | 1 | 1 | 0% | 2,812 | 7,037 | +150% | 0 | 0 | — |
case-21 | pass→pass | 17,966 | 17,647 | -2% | 1 | 1 | 0% | 2,709 | 6,990 | +158% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +18 percentage points is the difference between those two pass rates over the 22 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.