[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JM36WFTSFN377MJQMDA0FW":3,"skill-same:01M6JM36WFTSFN377MJQMDA0FW":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6JM36WFTSFN377MJQMDA0FW","plan-my-day",null,"Generate an energy-optimized, time-blocked daily plan based on circadian rhythm research and GTD principles","LongLeo287\u002FOmniClaw","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M6JK75GQ78TSP1ZPXNKK3MCH",9,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fplan_my_day\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"plan","plan my day","my","research","generate","planning","productivity","management","daily","time-blocking","energy-management","time","daily plan","gtd","principles","2026-11-10 10:12:30",false,"---\nname: plan-my-day\ndescription: Generate an energy-optimized, time-blocked daily plan based on circadian rhythm research and GTD principles\nversion: 2.0.0\nauthor: theflohart\ntags: [productivity, planning, time-blocking, energy-management, gtd]\n---\n\n# Plan My Day\n\nGenerate a clean, actionable hour-by-hour plan for the day based on priorities, energy patterns, and constraints.\n\n## Mode\n\nDetect from context or ask: *\"Quick priorities, full day plan, or full plan + weekly structure?\"*\n\n| Mode | What you get | Best for |\n|------|-------------|----------|\n| `quick` | Top 3 priorities + rough time blocks, 2 min | Morning sprint, already know the day |\n| `standard` | Full hour-by-hour energy-optimized plan | Default daily planning |\n| `deep` | Full plan + energy pattern analysis + weekly structure recommendations | Overhauling your schedule, high-performance week |\n\n**Default: `standard`** — use `quick` if they say \"just help me prioritize.\" Use `deep` if they want to rethink their week, not just plan today.\n\n---\n\n## Why This vs ChatGPT?\n\n**Problem with \"just asking\":** You get a different plan each time. No consistency, no memory of what works, no optimization over time.\n\n**This skill provides:**\n1. **Consistent methodology** - Same decision framework every day (Top 3 priorities, energy windows, buffer rules)\n2. **Energy-aware scheduling** - Automatically matches high-cognitive tasks to your peak hours\n3. **Constraint-aware** - Respects your existing calendar, energy patterns, personal boundaries\n4. **Learning memory** - Can track what scheduling patterns work best for you over time\n5. **Evening reflection built-in** - Forces accountability on what actually got done\n\n**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.\n\n## Usage\n\n```\n\u002Fplan-my-day [optional: YYYY-MM-DD for future date]\n```\n\nWith custom energy profile:\n\n```\n\u002Fplan-my-day --peak 9-11,14-16 --recovery 13-14\n```\n\n## Planning Principles (Research-Backed)\n\n1. **Circadian optimization** - Cognitive performance peaks ~2-3 hours after waking (Roenneberg, 2012)\n2. **Ultradian rhythms** - Work in 90-minute blocks with 15-20 minute breaks (Ericsson, 1993)\n3. **Decision fatigue prevention** - Schedule high-stakes decisions before 3pm (Kahneman, 2011)\n4. **Implementation intentions** - Specific time+task combinations increase completion by 2-3× (Gollwitzer, 1999)\n\n## Energy Windows (Default - Customize Yours)\n\n**Peak Performance (Morning):** 9:00 AM - 12:00 PM\n- Deep work, strategic thinking, complex problem-solving\n- Highest cognitive capacity\n- Schedule your #1 priority here\n\n**Secondary Peak (Afternoon):** 2:00 PM - 4:00 PM\n- Focused work, meetings with decisions, creative work\n- Still high capacity but slightly lower than morning\n\n**Administrative (Late Afternoon):** 4:00 PM - 6:00 PM\n- Email processing, light tasks, 1-on-1s, planning\n- Lower energy, avoid complex decisions\n\n**Recovery Blocks:** 12:00 PM - 1:00 PM, 6:00 PM+\n- Meals, exercise, walks, recharge\n- Non-negotiable for sustained performance\n\n**Wind Down (Evening):** After 7:00 PM\n- Reflection, reading, light planning for tomorrow\n- No high-cognitive work\n\n## Process\n\n### 1. Gather Context (30 seconds)\n- Check existing calendar events\n- Review yesterday's incomplete tasks\n- Identify any fixed commitments or deadlines\n- Note current project priorities\n\n### 2. Identify Top 3 Priorities (60 seconds)\nAsk for each potential priority:\n- **Impact:** Does this move a key metric or deadline?\n- **Urgency:** Must it happen today?\n- **Effort:** Can I complete it in available time?\n\n**Filter:** Pick the 3 with highest impact×urgency score\n\n### 3. Build Time-Blocked Schedule (90 seconds)\n**Sequencing logic:**\n1. Place fixed commitments (meetings, calls) first\n2. Assign Priority #1 to longest peak energy block\n3. Assign Priority #2 to secondary peak or next available\n4. Assign Priority #3 to remaining focused time\n5. Add 20-minute buffers between major blocks\n6. Schedule admin work (email, Slack) in low-energy windows\n7. Protect breaks and meals (non-negotiable)\n\n**Buffer rule:** Only schedule 80% of available time\n\n### 4. Apply Constraints\n- **Personal boundaries:** No work before 8am or after 7pm (customize)\n- **Meeting limits:** Max 4 hours of meetings per day\n- **Focus blocks:** Minimum 90 minutes for deep work (no interruptions)\n- **Break enforcement:** 15-minute break every 90 minutes\n\n## Output Format\n\n```markdown\n# Daily Plan - [Day], [Month] [Date], [Year]\n\n## Today's Mission\n\n**Primary Goal:** [One-sentence outcome for the day]\n\n**Top 3 Priorities:**\n1. [Priority 1 with specific, measurable outcome]\n2. [Priority 2 with specific, measurable outcome]\n3. [Priority 3 with specific, measurable outcome]\n\n**Success looks like:** [What \"done\" means today]\n\n---\n\n## Time-Blocked Schedule\n\n### 8:00 - 9:00: Morning Prime ?\n**Focus:** Wake up, coffee, light movement, review plan\n\n- [ ] Morning routine (30 min)\n- [ ] Review today's plan + priorities (10 min)\n- [ ] Quick inbox scan (15 min - flag only, don't respond)\n\n**Energy level:** Building\n\n---\n\n### 9:00 - 11:00: Deep Work Block 1 ? [PRIORITY #1]\n**Focus:** [Specific priority 1 task]\n\n- [ ] [Concrete subtask 1]\n- [ ] [Concrete subtask 2]\n- [ ] [Concrete subtask 3]\n\n**Target:** [Measurable outcome by 11:00]\n\n**Protection:** Phone off, Slack paused, door closed\n\n---\n\n### 11:00 - 11:15: Break ☕\n**Focus:** Step away from desk\n\n- Physical movement (walk, stretch)\n- Hydrate\n- No screens\n\n---\n\n### 11:15 - 12:30: Deep Work Block 2 ? [PRIORITY #2]\n**Focus:** [Specific priority 2 task]\n\n- [ ] [Concrete subtask 1]\n- [ ] [Concrete subtask 2]\n\n**Target:** [Measurable outcome by 12:30]\n\n---\n\n### 12:30 - 1:30: Lunch Break ?️\n**Focus:** Eat, recharge, disconnect\n\n- Proper meal (not at desk)\n- 15-minute walk if possible\n- No work talk\n\n**Energy level:** Recovery\n\n---\n\n### 1:30 - 3:00: Focused Work Block ? [PRIORITY #3]\n**Focus:** [Specific priority 3 task]\n\n- [ ] [Concrete subtask 1]\n- [ ] [Concrete subtask 2]\n\n**Target:** [Measurable outcome by 3:00]\n\n---\n\n### 3:00 - 3:15: Break ☕\n**Focus:** Recharge\n\n---\n\n### 3:15 - 4:30: Meetings \u002F Collaborative Work ?\n**Focus:** [Meeting name or collaborative task]\n\n- [ ] [Meeting 1 with agenda]\n- [ ] [Follow-up actions from meetings]\n\n**Prep:** Review agendas 10 minutes before\n\n---\n\n### 4:30 - 5:30: Admin & Communication ?\n**Focus:** Process inbox, respond to messages, light tasks\n\n- [ ] Clear email inbox (respond, archive, defer)\n- [ ] Slack catch-up and responses\n- [ ] Update project trackers\n- [ ] Quick wins \u002F small tasks\n\n**Energy level:** Lower (perfect for admin)\n\n---\n\n### 5:30 - 6:00: Planning & Wrap-Up ?\n**Focus:** Close the day, plan tomorrow\n\n- [ ] Evening check-in (see below)\n- [ ] Tomorrow's top 3 priorities draft\n- [ ] Inbox zero for peace of mind\n- [ ] Close all work apps\n\n---\n\n### 6:00 PM+: Personal Time ?\n**No work beyond this point**\n\n---\n\n## Success Criteria\n\n### Must-Have (Non-Negotiable) ✓\n- [ ] Priority 1 complete: [Specific outcome]\n- [ ] Priority 2 complete: [Specific outcome]\n- [ ] At least 80% progress on Priority 3\n\n### Should-Have (Important) ⭐\n- [ ] [Secondary task 1]\n- [ ] [Secondary task 2]\n\n### Nice-to-Have (Bonus) ?\n- [ ] [Bonus task 1]\n- [ ] [Bonus task 2]\n\n---\n\n## Evening Check-In (5 minutes at 5:30 PM)\n\n**Completion status:**\n- Priority 1 done? **YES \u002F NO** - [If no, why?]\n- Priority 2 done? **YES \u002F NO** - [If no, why?]\n- Priority 3 done? **YES \u002F NO** - [If no, why?]\n\n**What went well:**\n[What worked today? What helped you execute?]\n\n**What got stuck:**\n[Where did you lose time? What blocked you?]\n\n**Energy assessment:**\n- Peak hours productive? **YES \u002F NO**\n- Breaks taken? **YES \u002F NO**\n- Felt energized or drained? **[Score 1-10]**\n\n**Tomorrow's adjustment:**\n[What to change in tomorrow's plan based on today?]\n\n---\n\n## Quick Decision Framework\n\n**Before saying YES to anything today:**\n\n1. **Is this one of my top 3 priorities?**\n   - YES → Schedule it in appropriate energy window\n   - NO → Go to #2\n\n2. **Does this directly support today's mission?**\n   - YES → Add to relevant time block\n   - NO → Go to #3\n\n3. **Can this wait until tomorrow?**\n   - YES → Add to tomorrow's list\n   - NO → Question if it's really urgent\n\n**If NO to all three → Decline or defer**\n\n---\n```\n\n## Real Examples\n\n### Example 1: High-Output Day (Founder\u002FExec)\n\n**Context:** Product launch week, high-stakes demos, team coordination\n\n```markdown\n## Top 3 Priorities:\n1. Finalize launch announcement (900 words, 3 versions) - DONE by 11:30\n2. Run partner demo with clear next steps - DONE by 3:00\n3. Team sprint planning with Q2 priorities set - DONE by 5:00\n\n## Schedule:\n- 9:00-11:30: Deep work → Launch copy (Priority #1)\n- 12:30-2:45: Partner demo prep + execution (Priority #2)\n- 3:00-4:45: Sprint planning with team (Priority #3)\n- 5:00-5:30: Email\u002Fadmin\u002Fwrap\n\n## Evening Check-In:\n✓ Priority 1: YES (shipped 3 versions, CEO approved)\n✓ Priority 2: YES (partner committed, contract signed)\n✓ Priority 3: YES (team aligned, stories pointed)\n\nWhat worked: Protected deep work time for writing, prepped demo thoroughly\nTomorrow: Start execution on sprint, less coordination overhead\n```\n\n### Example 2: Deep Work Day (Individual Contributor)\n\n**Context:** IC developer, needs 6+ hours of uninterrupted coding\n\n```markdown\n## Top 3 Priorities:\n1. Ship authentication refactor (PR ready for review) - DONE by 12:00\n2. Debug production issue #847 (root cause found + fix deployed) - DONE by 4:00\n3. Documentation for new API endpoints (published) - DONE by 6:00\n\n## Schedule:\n- 9:00-12:00: Deep work → Auth refactor (Priority #1)\n- 1:00-4:00: Deep work → Debug + deploy (Priority #2)\n- 4:15-5:45: Documentation writing (Priority #3)\n- 5:45-6:00: Update tickets, close day\n\n## Protections:\n- Slack: Paused 9am-12pm, 1pm-4pm\n- No meetings scheduled\n- Phone: DND mode\n\n## Evening Check-In:\n✓ Priority 1: YES (PR approved, merged)\n✓ Priority 2: YES (issue resolved, monitoring green)\n✓ Priority 3: 90% (docs drafted, needs final review tomorrow)\n\nWhat worked: Zero meetings = maximum flow state\nTomorrow: Finish docs, start new feature work\n```\n\n### Example 3: Meeting-Heavy Day (Manager\u002FDirector)\n\n**Context:** Leadership role, multiple teams, coordination day\n\n```markdown\n## Top 3 Priorities:\n1. Align exec team on Q2 budget priorities - DONE by 11:00\n2. Resolve team conflict (performance conversation) - DONE by 3:00\n3. Approve 3 critical design reviews - DONE by 5:30\n\n## Schedule:\n- 8:30-9:00: Pre-meeting prep (agendas, talking points)\n- 9:00-11:00: Exec budget meeting (Priority #1)\n- 11:15-12:15: 1-on-1 performance conversation (Priority #2)\n- 1:30-3:00: Design review meetings (Priority #3, all 3 back-to-back)\n- 3:15-4:30: Email\u002Fadmin\u002Ffollow-ups from meetings\n- 4:30-5:00: Next week prep + team updates\n\n## Evening Check-In:\n✓ Priority 1: YES (budget approved, owners assigned)\n✓ Priority 2: YES (performance plan agreed, follow-up scheduled)\n✓ Priority 3: YES (2 approved, 1 needs revision)\n\nWhat got stuck: Back-to-back meetings = no thinking time\nTomorrow: Block 2-hour deep work window, fewer meetings\n```\n\n## Real Case Study\n\n**User:** Marketing manager at B2B SaaS company, struggled with reactive days\n\n**Before using skill:**\n- Average day: 6-8 hours in meetings, 2 hours of \"work\" squeezed in\n- Top priorities rarely completed\n- Constant email\u002FSlack interruptions\n- 15% weekly goal completion rate\n- Felt productive but accomplished little\n\n**After implementing plan-my-day:**\n- Used skill every morning (2-3 minutes to generate plan)\n- Protected 9-11am deep work block (calendar marked \"Focus Time\")\n- Set clear Top 3 priorities each day\n- Added evening check-ins to track completion\n\n**Results after 8 weeks:**\n- 74% weekly goal completion rate (+59 points)\n- Meetings reduced from 6-8 hrs\u002Fday to 3-4 hrs\u002Fday\n- Deep work blocks protected 4 days\u002Fweek (vs 0 before)\n- Self-reported energy levels: 8.2\u002F10 (vs 4.1\u002F10 before)\n- Team feedback: \"You're more present and decisive\"\n\n**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.\"\n\n## Configuration Options\n\n### Standard Mode (default)\n```\n\u002Fplan-my-day\n```\n- Balanced energy windows\n- 8-hour workday assumption\n- 20% buffer time\n\n### High-Output Mode\n```\n\u002Fplan-my-day --mode high-output\n```\n- 10-hour workday\n- More aggressive scheduling\n- 10% buffer time\n- Best for: Launch weeks, crunch periods\n\n### Deep Work Mode\n```\n\u002Fplan-my-day --mode deep-work\n```\n- Maximum uninterrupted blocks\n- Minimal meetings\n- 30% buffer time\n- Best for: Individual contributors, creators\n\n### Meeting-Heavy Mode\n```\n\u002Fplan-my-day --mode coordination\n```\n- Meeting-first scheduling\n- Work blocks fit around commitments\n- 25% buffer time\n- Best for: Managers, executives, client-facing roles\n\n## Installation\n\n```bash\n# Copy skill to your skills directory\ncp -r plan-my-day $HOME\u002F.openclaw\u002Fskills\u002F\n\n# Verify installation\n\u002Fplan-my-day --version\n```\n\n**No dependencies required** - Pure planning logic.\n\n## Future Integrations (Coming Soon)\n\n- **Google Calendar sync** - Auto-import existing events\n- **Completion tracking** - Analytics on your planning accuracy over time\n- **Energy pattern learning** - Adapts to when you actually perform best\n- **Team coordination** - Sync focus blocks across teams\n\n## Pro Tips\n\n1. **Run it FIRST thing** - Before checking email or Slack. Set the day, don't react to it.\n2. **Protect Peak hours** - Block 9-11am as \"Focus Time\" on your calendar. Decline meetings here.\n3. **Track completion rates** - Use evening check-in data to improve your estimations\n4. **Adjust energy windows** - Default is 9-11am peak, but if you're different, customize it\n5. **Combine with \"shutdown ritual\"** - Evening check-in + tomorrow's prep = mental closure\n6. **Don't over-schedule** - If plan shows 7 hours of tasks for 8-hour day, you're on track\n\n## Common Mistakes to Avoid\n\n❌ **Planning too much** - If you schedule 100% of your time, you'll fail. Always leave 20% buffer.\n❌ **Ignoring energy windows** - Putting hard thinking work at 4pm sets you up for failure.\n❌ **Skipping breaks** - 90-minute focus blocks REQUIRE 15-minute breaks or performance drops.\n❌ **No evening reflection** - Without check-ins, you can't improve your planning accuracy.\n❌ **Changing Top 3 mid-day** - Unless genuinely urgent, stick to morning priorities.\n\n## Quality Checklist\n\nA good daily plan has:\n- [ ] Clear Top 3 priorities with measurable outcomes\n- [ ] #1 priority scheduled in peak energy window\n- [ ] 20% buffer time (not every minute scheduled)\n- [ ] Breaks scheduled every 90 minutes\n- [ ] Protected lunch break (minimum 30 minutes)\n- [ ] Evening check-in template included\n- [ ] No work scheduled after 7pm (personal time protected)\n\n## Support\n\nIssues or suggestions? Provide:\n- Your typical day structure (work hours, meeting load)\n- Top 3 priorities example\n- Energy pattern (when you're most focused)\n- What's not working in current output\n\n---\n\n**Built on circadian rhythm research (Roenneberg), deliberate practice principles (Ericsson), and GTD methodology (Allen).**\n\n**Plan your day in 2 minutes. Execute with focus. Win consistently.**","# Plan My Day\n\nGenerate a clean, actionable hour-by-hour plan for the day based on priorities, energy patterns, and constraints.\n\n## Mode\n\nDetect from context or ask: *\"Quick priorities, full day plan, or full plan + weekly structure?\"*\n\n| Mode | What you get | Best for |\n|------|-------------|----------|\n| `quick` | Top 3 priorities + rough time blocks, 2 min | Morning sprint, already know the day |\n| `standard` | Full hour-by-hour energy-optimized plan | Default daily planning |\n| `deep` | Full plan + energy pattern analysis + weekly structure recommendations | Overhauling your schedule, high-performance week |\n\n**Default: `standard`** — use `quick` if they say \"just help me prioritize.\" Use `deep` if they want to rethink their week, not just plan today.\n\n---\n\n## Why This vs ChatGPT?\n\n**Problem with \"just asking\":** You get a different plan each time. No consistency, no memory of what works, no optimization over time.\n\n**This skill provides:**\n1. **Consistent methodology** - Same decision framework every day (Top 3 priorities, energy windows, buffer rules)\n2. **Energy-aware scheduling** - Automatically matches high-cognitive tasks to your peak hours\n3. **Constraint-aware** - Respects your existing calendar, energy patterns, personal boundaries\n4. **Learning memory** - Can track what scheduling patterns work best for you over time\n5. **Evening reflection built-in** - Forces accountability on what actually got done\n\n**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.\n\n## Usage\n\n```\n\u002Fplan-my-day [optional: YYYY-MM-DD for future date]\n```\n\nWith custom energy profile:\n\n```\n\u002Fplan-my-day --peak 9-11,14-16 --recovery 13-14\n```\n\n## Planning Principles (Research-Backed)\n\n1. **Circadian optimization** - Cognitive performance peaks ~2-3 hours after waking (Roenneberg, 2012)\n2. **Ultradian rhythms** - Work in 90-minute blocks with 15-20 minute breaks (Ericsson, 1993)\n3. **Decision fatigue prevention** - Schedule high-stakes decisions before 3pm (Kahneman, 2011)\n4. **Implementation intentions** - Specific time+task combinations increase completion by 2-3× (Gollwitzer, 1999)\n\n## Energy Windows (Default - Customize Yours)\n\n**Peak Performance (Morning):** 9:00 AM - 12:00 PM\n- Deep work, strategic thinking, complex problem-solving\n- Highest cognitive capacity\n- Schedule your #1 priority here\n\n**Secondary Peak (Afternoon):** 2:00 PM - 4:00 PM\n- Focused work, meetings with decisions, creative work\n- Still high capacity but slightly lower than morning\n\n**Administrative (Late Afternoon):** 4:00 PM - 6:00 PM\n- Email processing, light tasks, 1-on-1s, planning\n- Lower energy, avoid complex decisions\n\n**Recovery Blocks:** 12:00 PM - 1:00 PM, 6:00 PM+\n- Meals, exercise, walks, recharge\n- Non-negotiable for sustained performance\n\n**Wind Down (Evening):** After 7:00 PM\n- Reflection, reading, light planning for tomorrow\n- No high-cognitive work\n\n## Process\n\n### 1. Gather Context (30 seconds)\n- Check existing calendar events\n- Review yesterday's incomplete tasks\n- Identify any fixed commitments or deadlines\n- Note current project priorities\n\n### 2. Identify Top 3 Priorities (60 seconds)\nAsk for each potential priority:\n- **Impact:** Does this move a key metric or deadline?\n- **Urgency:** Must it happen today?\n- **Effort:** Can I complete it in available time?\n\n**Filter:** Pick the 3 with highest impact×urgency score\n\n### 3. Build Time-Blocked Schedule (90 seconds)\n**Sequencing logic:**\n1. Place fixed commitments (meetings, calls) first\n2. Assign Priority #1 to longest peak energy block\n3. Assign Priority #2 to secondary peak or next available\n4. Assign Priority #3 to remaining focused time\n5. Add 20-minute buffers between major blocks\n6. Schedule admin work (email, Slack) in low-energy windows\n7. Protect breaks and meals (non-negotiable)\n\n**Buffer rule:** Only schedule 80% of available time\n\n### 4. Apply Constraints\n- **Personal boundaries:** No work before 8am or after 7pm (customize)\n- **Meeting limits:** Max 4 hours of meetings per day\n- **Focus blocks:** Minimum 90 minutes for deep work (no interruptions)\n- **Break enforcement:** 15-minute break every 90 minutes\n\n## Output Format\n\n```markdown\n# Daily Plan - [Day], [Month] [Date], [Year]\n\n## Today's Mission\n\n**Primary Goal:** [One-sentence outcome for the day]\n\n**Top 3 Priorities:**\n1. [Priority 1 with specific, measurable outcome]\n2. [Priority 2 with specific, measurable outcome]\n3. [Priority 3 with specific, measurable outcome]\n\n**Success looks like:** [What \"done\" means today]\n\n---\n\n## Time-Blocked Schedule\n\n### 8:00 - 9:00: Morning Prime ?\n**Focus:** Wake up, coffee, light movement, review plan\n\n- [ ] Morning routine (30 min)\n- [ ] Review today's plan + priorities (10 min)\n- [ ] Quick inbox scan (15 min - flag only, don't respond)\n\n**Energy level:** Building\n\n---\n\n### 9:00 - 11:00: Deep Work Block 1 ? [PRIORITY #1]\n**Focus:** [Specific priority 1 task]\n\n- [ ] [Concrete subtask 1]\n- [ ] [Concrete subtask 2]\n- [ ] [Concrete subtask 3]\n\n**Target:** [Measurable outcome by 11:00]\n\n**Protection:** Phone off, Slack paused, door closed\n\n---\n\n### 11:00 - 11:15: Break ☕\n**Focus:** Step away from desk\n\n- Physical movement (walk, stretch)\n- Hydrate\n- No screens\n\n---\n\n### 11:15 - 12:30: Deep Work Block 2 ? [PRIORITY #2]\n**Focus:** [Specific priority 2 task]\n\n- [ ] [Concrete subtask 1]\n- [ ] [Concrete subtask 2]\n\n**Target:** [Measurable outcome by 12:30]\n\n---\n\n### 12:30 - 1:30: Lunch Break ?️\n**Focus:** Eat, recharge, disconnect\n\n- Proper meal (not at desk)\n- 15-minute walk if possible\n- No work talk\n\n**Energy level:** Recovery\n\n---\n\n### 1:30 - 3:00: Focused Work Block ? [PRIORITY #3]\n**Focus:** [Specific priority 3 task]\n\n- [ ] [Concrete subtask 1]\n- [ ] [Concrete subtask 2]\n\n**Target:** [Measurable outcome by 3:00]\n\n---\n\n### 3:00 - 3:15: Break ☕\n**Focus:** Recharge\n\n---\n\n### 3:15 - 4:30: Meetings \u002F Collaborative Work ?\n**Focus:** [Meeting name or collaborative task]\n\n- [ ] [Meeting 1 with agenda]\n- [ ] [Follow-up actions from meetings]\n\n**Prep:** Review agendas 10 minutes before\n\n---\n\n### 4:30 - 5:30: Admin & Communication ?\n**Focus:** Process inbox, respond to messages, light tasks\n\n- [ ] Clear email inbox (respond, archive, defer)\n- [ ] Slack catch-up and responses\n- [ ] Update project trackers\n- [ ] Quick wins \u002F small tasks\n\n**Energy level:** Lower (perfect for admin)\n\n---\n\n### 5:30 - 6:00: Planning & Wrap-Up ?\n**Focus:** Close the day, plan tomorrow\n\n- [ ] Evening check-in (see below)\n- [ ] Tomorrow's top 3 priorities draft\n- [ ] Inbox zero for peace of mind\n- [ ] Close all work apps\n\n---\n\n### 6:00 PM+: Personal Time ?\n**No work beyond this point**\n\n---\n\n## Success Criteria\n\n### Must-Have (Non-Negotiable) ✓\n- [ ] Priority 1 complete: [Specific outcome]\n- [ ] Priority 2 complete: [Specific outcome]\n- [ ] At least 80% progress on Priority 3\n\n### Should-Have (Important) ⭐\n- [ ] [Secondary task 1]\n- [ ] [Secondary task 2]\n\n### Nice-to-Have (Bonus) ?\n- [ ] [Bonus task 1]\n- [ ] [Bonus task 2]\n\n---\n\n## Evening Check-In (5 minutes at 5:30 PM)\n\n**Completion status:**\n- Priority 1 done? **YES \u002F NO** - [If no, why?]\n- Priority 2 done? **YES \u002F NO** - [If no, why?]\n- Priority 3 done? **YES \u002F NO** - [If no, why?]\n\n**What went well:**\n[What worked today? What helped you execute?]\n\n**What got stuck:**\n[Where did you lose time? What blocked you?]\n\n**Energy assessment:**\n- Peak hours productive? **YES \u002F NO**\n- Breaks taken? **YES \u002F NO**\n- Felt energized or drained? **[Score 1-10]**\n\n**Tomorrow's adjustment:**\n[What to change in tomorrow's plan based on today?]\n\n---\n\n## Quick Decision Framework\n\n**Before saying YES to anything today:**\n\n1. **Is this one of my top 3 priorities?**\n   - YES → Schedule it in appropriate energy window\n   - NO → Go to #2\n\n2. **Does this directly support today's mission?**\n   - YES → Add to relevant time block\n   - NO → Go to #3\n\n3. **Can this wait until tomorrow?**\n   - YES → Add to tomorrow's list\n   - NO → Question if it's really urgent\n\n**If NO to all three → Decline or defer**\n\n---\n```\n\n## Real Examples\n\n### Example 1: High-Output Day (Founder\u002FExec)\n\n**Context:** Product launch week, high-stakes demos, team coordination\n\n```markdown\n## Top 3 Priorities:\n1. Finalize launch announcement (900 words, 3 versions) - DONE by 11:30\n2. Run partner demo with clear next steps - DONE by 3:00\n3. Team sprint planning with Q2 priorities set - DONE by 5:00\n\n## Schedule:\n- 9:00-11:30: Deep work → Launch copy (Priority #1)\n- 12:30-2:45: Partner demo prep + execution (Priority #2)\n- 3:00-4:45: Sprint planning with team (Priority #3)\n- 5:00-5:30: Email\u002Fadmin\u002Fwrap\n\n## Evening Check-In:\n✓ Priority 1: YES (shipped 3 versions, CEO approved)\n✓ Priority 2: YES (partner committed, contract signed)\n✓ Priority 3: YES (team aligned, stories pointed)\n\nWhat worked: Protected deep work time for writing, prepped demo thoroughly\nTomorrow: Start execution on sprint, less coordination overhead\n```\n\n### Example 2: Deep Work Day (Individual Contributor)\n\n**Context:** IC developer, needs 6+ hours of uninterrupted coding\n\n```markdown\n## Top 3 Priorities:\n1. Ship authentication refactor (PR ready for review) - DONE by 12:00\n2. Debug production issue #847 (root cause found + fix deployed) - DONE by 4:00\n3. Documentation for new API endpoints (published) - DONE by 6:00\n\n## Schedule:\n- 9:00-12:00: Deep work → Auth refactor (Priority #1)\n- 1:00-4:00: Deep work → Debug + deploy (Priority #2)\n- 4:15-5:45: Documentation writing (Priority #3)\n- 5:45-6:00: Update tickets, close day\n\n## Protections:\n- Slack: Paused 9am-12pm, 1pm-4pm\n- No meetings scheduled\n- Phone: DND mode\n\n## Evening Check-In:\n✓ Priority 1: YES (PR approved, merged)\n✓ Priority 2: YES (issue resolved, monitoring green)\n✓ Priority 3: 90% (docs drafted, needs final review tomorrow)\n\nWhat worked: Zero meetings = maximum flow state\nTomorrow: Finish docs, start new feature work\n```\n\n### Example 3: Meeting-Heavy Day (Manager\u002FDirector)\n\n**Context:** Leadership role, multiple teams, coordination day\n\n```markdown\n## Top 3 Priorities:\n1. Align exec team on Q2 budget priorities - DONE by 11:00\n2. Resolve team conflict (performance conversation) - DONE by 3:00\n3. Approve 3 critical design reviews - DONE by 5:30\n\n## Schedule:\n- 8:30-9:00: Pre-meeting prep (agendas, talking points)\n- 9:00-11:00: Exec budget meeting (Priority #1)\n- 11:15-12:15: 1-on-1 performance conversation (Priority #2)\n- 1:30-3:00: Design review meetings (Priority #3, all 3 back-to-back)\n- 3:15-4:30: Email\u002Fadmin\u002Ffollow-ups from meetings\n- 4:30-5:00: Next week prep + team updates\n\n## Evening Check-In:\n✓ Priority 1: YES (budget approved, owners assigned)\n✓ Priority 2: YES (performance plan agreed, follow-up scheduled)\n✓ Priority 3: YES (2 approved, 1 needs revision)\n\nWhat got stuck: Back-to-back meetings = no thinking time\nTomorrow: Block 2-hour deep work window, fewer meetings\n```\n\n## Real Case Study\n\n**User:** Marketing manager at B2B SaaS company, struggled with reactive days\n\n**Before using skill:**\n- Average day: 6-8 hours in meetings, 2 hours of \"work\" squeezed in\n- Top priorities rarely completed\n- Constant email\u002FSlack interruptions\n- 15% weekly goal completion rate\n- Felt productive but accomplished little\n\n**After implementing plan-my-day:**\n- Used skill every morning (2-3 minutes to generate plan)\n- Protected 9-11am deep work block (calendar marked \"Focus Time\")\n- Set clear Top 3 priorities each day\n- Added evening check-ins to track completion\n\n**Results after 8 weeks:**\n- 74% weekly goal completion rate (+59 points)\n- Meetings reduced from 6-8 hrs\u002Fday to 3-4 hrs\u002Fday\n- Deep work blocks protected 4 days\u002Fweek (vs 0 before)\n- Self-reported energy levels: 8.2\u002F10 (vs 4.1\u002F10 before)\n- Team feedback: \"You're more present and decisive\"\n\n**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.\"\n\n## Configuration Options\n\n### Standard Mode (default)\n```\n\u002Fplan-my-day\n```\n- Balanced energy windows\n- 8-hour workday assumption\n- 20% buffer time\n\n### High-Output Mode\n```\n\u002Fplan-my-day --mode high-output\n```\n- 10-hour workday\n- More aggressive scheduling\n- 10% buffer time\n- Best for: Launch weeks, crunch periods\n\n### Deep Work Mode\n```\n\u002Fplan-my-day --mode deep-work\n```\n- Maximum uninterrupted blocks\n- Minimal meetings\n- 30% buffer time\n- Best for: Individual contributors, creators\n\n### Meeting-Heavy Mode\n```\n\u002Fplan-my-day --mode coordination\n```\n- Meeting-first scheduling\n- Work blocks fit around commitments\n- 25% buffer time\n- Best for: Managers, executives, client-facing roles\n\n## Installation\n\n```bash\n# Copy skill to your skills directory\ncp -r plan-my-day $HOME\u002F.openclaw\u002Fskills\u002F\n\n# Verify installation\n\u002Fplan-my-day --version\n```\n\n**No dependencies required** - Pure planning logic.\n\n## Future Integrations (Coming Soon)\n\n- **Google Calendar sync** - Auto-import existing events\n- **Completion tracking** - Analytics on your planning accuracy over time\n- **Energy pattern learning** - Adapts to when you actually perform best\n- **Team coordination** - Sync focus blocks across teams\n\n## Pro Tips\n\n1. **Run it FIRST thing** - Before checking email or Slack. Set the day, don't react to it.\n2. **Protect Peak hours** - Block 9-11am as \"Focus Time\" on your calendar. Decline meetings here.\n3. **Track completion rates** - Use evening check-in data to improve your estimations\n4. **Adjust energy windows** - Default is 9-11am peak, but if you're different, customize it\n5. **Combine with \"shutdown ritual\"** - Evening check-in + tomorrow's prep = mental closure\n6. **Don't over-schedule** - If plan shows 7 hours of tasks for 8-hour day, you're on track\n\n## Common Mistakes to Avoid\n\n❌ **Planning too much** - If you schedule 100% of your time, you'll fail. Always leave 20% buffer.\n❌ **Ignoring energy windows** - Putting hard thinking work at 4pm sets you up for failure.\n❌ **Skipping breaks** - 90-minute focus blocks REQUIRE 15-minute breaks or performance drops.\n❌ **No evening reflection** - Without check-ins, you can't improve your planning accuracy.\n❌ **Changing Top 3 mid-day** - Unless genuinely urgent, stick to morning priorities.\n\n## Quality Checklist\n\nA good daily plan has:\n- [ ] Clear Top 3 priorities with measurable outcomes\n- [ ] #1 priority scheduled in peak energy window\n- [ ] 20% buffer time (not every minute scheduled)\n- [ ] Breaks scheduled every 90 minutes\n- [ ] Protected lunch break (minimum 30 minutes)\n- [ ] Evening check-in template included\n- [ ] No work scheduled after 7pm (personal time protected)\n\n## Support\n\nIssues or suggestions? Provide:\n- Your typical day structure (work hours, meeting load)\n- Top 3 priorities example\n- Energy pattern (when you're most focused)\n- What's not working in current output\n\n---\n\n**Built on circadian rhythm research (Roenneberg), deliberate practice principles (Ericsson), and GTD methodology (Allen).**\n\n**Plan your day in 2 minutes. Execute with focus. Win consistently.**",{"name":5,"tags":44,"author":45,"version":46,"description":7},[30,29,33,34,37],"theflohart","2.0.0","main","c173cdffe08e788a99b91928a831b476b8434838","ecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fplan_my_day",0,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw","https:\u002F\u002Fportfolio-longleo.vercel.app\u002Flabs\u002Fomniclaw.html","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-09-30 00:58:05",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add LongLeo287\u002FOmniClaw --skill plan-my-day",{"tool":62,"command":63},"bunx","bunx skills add LongLeo287\u002FOmniClaw --skill plan-my-day",{"tool":65,"command":66},"pnpm","pnpm dlx skills add LongLeo287\u002FOmniClaw --skill plan-my-day","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fplan_my_day\u002FSKILL.md",true,[70,76,80,84],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"_DIR_IDENTITY.md","REFERENCE","参考文档",358,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fplan_my_day\u002F_DIR_IDENTITY.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"meta.json",275,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fplan_my_day\u002Fmeta.json",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"README.md",8148,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fplan_my_day\u002FREADME.md",{"path":85,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":86,"sourceHtmlUrl":87},"skill_oc.md",2212,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fplan_my_day\u002Fskill_oc.md",[89,130,152,179,195,221],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":109,"publishedAt":39},"01M6JR0KQP4MHT32TN40D9CBFX","UI-UX Pro Max","Advanced UI\u002FUX analysis and generation skills with data-driven patterns. Python scripts (core.py, search.py) for systematic UI pattern extraction, design system generation, and component search from curated data sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fui_ux_pro_max\u002FSKILL.md",[95,98,101,106],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":107,"categoryName":108,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000033","数据分析师",[110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129],"ux","ui","ui ux pro max","max","pro","ui ux","design","component","search","analysis","team","rd","ui-ux","active","systematic","scripts","pattern extraction","sources","advanced","data-driven",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":39},"01M6JR0EF5AEQHP2FSTB57H05P","shadcn-ui","Expert guidance for integrating and building applications with shadcn\u002Fui components, including component discovery, installation, customization, and best practices.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fshadcn_ui\u002FSKILL.md",[136],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[138,111,139,140,117,141,142,143,144,120,145,146,147,123,148,149,150,151],"shadcn","shadcn ui","components","core","best practices","applications","discovery","customization","guidance","expert","installation","ui components","with","for",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":39},"01M6JR08F51BEN17RHFYX65WVE","zustand_store_ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand_store_ts\u002FSKILL.md",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[162,163,164,165,166,167,168,169,170,171,31,172,173,174,175,176,150,177,178],"zustand store ts","zustand","store","typescript","microsoft","react","create","state management","state","react state management","global","use","patterns","separation","middleware","action","implementing",{"skillNo":180,"name":163,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":39},"01M6JR00TDMVAFFCZXZ04AN7Q7","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand\u002FSKILL.md",[],[163,185,169,186,170,187,188,31,189,173,190,191,192,164,150,193,194,177,178],"development","code","actions","src","guide","implementation","zustand state","triggers","questions","zustand state management",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":205,"publishedAt":39},"01M6JQZSWV4KWJP112G6XHEP44","youtube_summarizer","Automatically fetch YouTube video transcripts, generate structured summaries, and send full transcripts to messaging platforms. Detects YouTube URLs and provides metadata, key insights, and downloadable transcripts.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_summarizer\u002FSKILL.md",[201,204],{"categoryNo":202,"categoryName":203,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},[206,207,208,28,209,210,211,212,213,214,215,216,217,218,219,220],"youtube","youtube summarizer","summarizer","metadata","messaging","Video","fetch","telegram","transcription","summarization","structured","full","insights","transcripts","summaries",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":39},"01M6JQZN3QJB6B77JGKJD62DQT","youtube_clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_clipper\u002FSKILL.md",[],[206,228,229,211,230,231,232,233,234,235,236,237,238,239,240,241,242],"clipper","youtube clipper","Bash","下载","视频","生成","关键词","翻译","read","write","clip","总结","工具","文案","sonnet"]