[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76W2VCDN3JRWF76KTYQSRPT":3,"skill-same:01M76W2VCDN3JRWF76KTYQSRPT":47},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M76W2VCDN3JRWF76KTYQSRPT","daily-plan",null,"Generate context-aware daily plan with calendar, tasks, and priorities. Includes midweek awareness, meeting intelligence, commitment tracking, and smart scheduling suggestions.","hemory\u002Famp","hemory","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21179881?v=4","01M6D31HFJ391DN8N0JP8AQGFE","Hemory Phifer","01M758Z6KK3NGD8654Y5CT668C",0,"MIT","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdaily-plan\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: daily-plan\ndescription: Generate context-aware daily plan with calendar, tasks, and priorities. Includes midweek awareness, meeting intelligence, commitment tracking, and smart scheduling suggestions.\ncontext: fork\n---\n\n## Purpose\n\nGenerate your daily plan with full context awareness. Automatically gathers information from your calendar, tasks, meetings, relationships, and weekly progress to create a focused plan with genuine situational awareness.\n\n## Usage\n\n- `\u002Fdaily-plan` — Create today's daily plan\n- `\u002Fdaily-plan tomorrow` — Plan for tomorrow (evening planning)\n- `\u002Fdaily-plan --setup` — Re-run integration setup\n\n**Batch limit:** Include at most 20 calendar events and 20 tasks in a single plan. Summarize overflow items as a count.\n\n---\n\n## Tone Calibration\n\nBefore executing this command, read `System\u002Fuser-profile.yaml` → `communication` section and adapt tone accordingly (see CLAUDE.md → \"Communication Adaptation\").\n\n---\n\n## Step 0: Demo Mode Check\n\nBefore anything else, check if demo mode is active:\n\n1. Read `System\u002Fuser-profile.yaml`\n2. Check `demo_mode` value\n3. **If `demo_mode: true`:**\n   - Display banner: \"Demo Mode Active — Using sample data from System\u002FDemo\u002F\"\n   - Use demo paths and skip live integrations\n4. **If `demo_mode: false`:** Proceed normally\n\n---\n\n## Step 0.5: Prerequisite Check — Calendar\n\nBefore generating the plan, check if calendar integration is configured:\n- Look for a `calendar_integration` key in `System\u002Fuser-profile.yaml`\n- OR check if calendar MCP tools are available (e.g., `calendar_get_today`)\n\n**If calendar is NOT configured**, add this note at the start of the plan output (before the greeting):\n\n> 💡 **Calendar integration available.** Your daily plan can include meetings and prep suggestions. Options:\n> - **Apple Calendar** (direct) — Fast, uses AppleScript\n> - **Apple Calendar via EventKit** — More reliable, needs permissions\n> - **Google Calendar** — For Google Workspace users\n>\n> Run `\u002Fcalendar-setup` to connect.\n\n**If calendar IS configured**, skip this note entirely. This hint is informational and does not block plan generation.\n\n---\n\n## Step 1: Background Checks (Silent)\n\nRun these silently without user-facing output:\n\n1. **Update check**: `check_for_updates(force=False)` - store notification if available\n2. **Self-learning checks**: Run changelog and learning review scripts if due\n3. **Search index refresh**: Run `qmd update && qmd embed` to refresh vault search index with any overnight changes (meetings processed, files edited, etc.). If `qmd` is not installed, skip silently.\n4. **People index refresh**: Call `build_people_index` from Work MCP. This keeps the People Directory current so person lookups throughout the day are fast. Takes \u003C2 seconds.\n5. **Innovation synthesis** (silent): Call `synthesize_changelog()` and `synthesize_learnings()` from Improvements MCP. These run in background and populate the backlog — results are surfaced in Step 1.5 below.\n6. **Granola migration check** (silent): Run `node .scripts\u002Fmeeting-intel\u002Fcheck-granola-migration.cjs 2>\u002Fdev\u002Fnull || echo '{\"status\":\"not_applicable\"}'`. If status is `migration_available`, store this fact and append a brief note at the END of the daily plan output (after all other sections): *\"Granola now syncs phone recordings too. Run `\u002Fprocess-meetings` to set it up.\"* If the script does not exist or returns any other status, skip silently. Never interrupt the planning flow for this check.\n\n---\n\n## Step 1.5: Innovation Spotlight (Concierge)\n\nAfter background checks complete, check for noteworthy backlog activity:\n\n1. Call `list_ideas(status=\"active\", min_score=70)` from Improvements MCP\n2. Check `System\u002F.synthesis-state.json` for recent synthesis activity (last 7 days)\n3. If there are AI-authored or recently enriched ideas, pick the most impactful one\n\n**Surface as a brief spotlight in the plan output (1-2 lines max):**\n\n> **Innovation Spotlight:** Claude Code shipped native memory (v2.1.32) — this could simplify idea-006 (Session Memory MCP). Run `\u002Famp-improve idea-006` to explore.\n\n**Rules:**\n- Show at most 1 spotlight per daily plan (don't overwhelm)\n- Rotate through ideas — don't show the same one twice in a row\n- Only show if there's genuine \"Why Now?\" urgency (new evidence in last 7 days)\n- If no recent synthesis activity, skip this section entirely\n- Never block the plan for this — it's a helpful aside, not a gate\n\n---\n\n## Step 2: Morning Journal Check (If Enabled)\n\nIf `journaling.morning: true` in user-profile.yaml, check for today's morning journal and prompt if missing.\n\n---\n\n## Step 3: Monday Weekly Planning Gate\n\nIf today is Monday and week isn't planned, offer to run `\u002Fweek-plan` first.\n\n---\n\n## Step 4: Yesterday's Review Check (Soft Gate)\n\nCheck for yesterday's review and extract context (open loops, tomorrow's focus, blocked items).\n\n---\n\n## Step 5: Context Gathering (ENHANCED)\n\nGather context from all available sources. **This is where the magic happens.**\n\n### 5.1 Midweek Progress Check (NEW)\n\n```\nUse: get_week_progress()\n```\n\nThis is critical for genuine situational awareness. Extract:\n- Day of week and days remaining\n- Weekly priority status (complete \u002F in_progress \u002F not_started)\n- Warnings for priorities with no activity\n\n**Surface this prominently:**\n\n> \"It's **Wednesday**. Here's where you are on this week's priorities:\n> \n> 1. ✅ **Ship pricing page** — Complete (finished Monday)\n> 2. 🔄 **Review proposal** — In progress (2 of 5 tasks done)\n> 3. ⚠️ **Customer interviews** — Not started (no activity yet)\n> \n> You have 2 days left this week. Priority 3 needs attention.\"\n\n### 5.2 Calendar Capacity Analysis (NEW)\n\n```\nUse: analyze_calendar_capacity(days_ahead=1, events=[...from calendar MCP...])\n```\n\nUnderstand the *shape* of today:\n\n- **Day type**: stacked \u002F moderate \u002F open\n- **Meeting count and hours**\n- **Free blocks available**\n- **Recommendation**: What kind of work fits today\n\n**Surface this:**\n\n> \"📅 **Today's shape:** Moderate (4 meetings, 3 hours total)\n> \n> **Free blocks:**\n> - 8:00-9:30 AM (90 min) — Morning focus time\n> - 2:00-4:00 PM (120 min) — Afternoon block\n> \n> **Recommendation:** Good for medium tasks and meeting prep. Deep work fits the 2-4pm block.\"\n\n### 5.3 Meeting Intelligence (NEW)\n\nFor each meeting today:\n\n```\nUse: get_meeting_context(meeting_title=\"...\", attendees=[...])\n```\n\nGet genuine context, not just attendee names:\n- **Related project**: What project is this connected to?\n- **Project status**: What's outstanding? What's blocked?\n- **Outstanding tasks with attendees**: What do you owe them? What do they owe you?\n- **Prep suggestions**: What should you review before this meeting?\n\n**Surface this with surprise and delight:**\n\n> \"📍 **Meeting: [Meeting Title]** (2pm with [Attendee 1], [Attendee 2])\n> \n> **Related project:** [Project Name]\n> - Status: On track, but [section] still in draft\n> - Outstanding: You owe [Attendee 1] the [deliverable]\n> \n> **Prep suggestion:** Review [relevant doc], prepare [talking points]. Block 30 min before this meeting?\"\n\n### 5.4 Commitment Tracking (NEW)\n\n```\nUse: get_commitments_due(date_range=\"today\")\n```\n\nSurface things you said you'd do:\n\n> \"⚡ **Commitments due today:**\n> \n> - You told [Person] you'd get back to them by Wednesday (from Monday 1:1)\n> - Follow up on [deliverable] (from [meeting name])\"\n\n### 5.5 Task Scheduling Suggestions (NEW)\n\n```\nUse: suggest_task_scheduling(include_all_tasks=False, calendar_events=[...])\n```\n\nMatch tasks to available time based on effort classification:\n\n> \"📋 **Scheduling suggestions:**\n> \n> | Task | Effort | Suggested Time |\n> |------|--------|----------------|\n> | Write Q1 strategy doc | Deep work (2-3h) | Tomorrow (you have a 3h morning block) |\n> | Review [Person]'s proposal | Medium (1h) | Today 2-3pm (before [meeting]) |\n> | Reply to [Person] | Quick (15min) | Between meetings |\n> \n> ⚠️ **Heads up:** You have 2 deep work tasks but today's too fragmented. Consider protecting tomorrow morning.\"\n\n### 5.6 Semantic Context Enrichment (if QMD available)\n\n**This step runs automatically when QMD is installed via `\u002Fenable-semantic-search`.** It adds a semantic search layer on top of the standard context gathering to surface connections that keyword search misses.\n\nCheck if QMD MCP tools are available by calling `qmd_status`. **If available:**\n\n1. **For each meeting today**, run:\n   ```\n   qmd_search(query=\"[meeting topic] [attendee names]\", limit=3)\n   ```\n   Surface: past discussions, related decisions, relevant commitments that share **meaning** but not keywords with this meeting. Example: a meeting about \"customer onboarding\" finds notes about \"activation rates\" and \"time to value\".\n\n2. **For each weekly priority that's lagging**, run:\n   ```\n   qmd_search(query=\"[priority description]\", limit=3)\n   ```\n   Surface: vault content that advances or relates to this priority but wouldn't appear in a keyword search. Especially useful for finding forgotten context about stalled work.\n\n3. **Cross-topic connection scan:**\n   ```\n   qmd_search(query=\"[today's key themes combined]\", limit=5)\n   ```\n   Surface: unexpected connections between today's meetings, tasks, and priorities. This is where semantic search shines — finding that a 2pm customer call relates to a PRD you wrote last month using completely different terminology.\n\n4. **Merge with existing context** — only add genuinely new insights. Don't duplicate what Steps 5.1-5.5 already found. Mark semantic results with their source so the plan output can distinguish them.\n\n**What this enables in the plan output:**\n- Meeting context sections include \"**Also relevant:**\" with thematically related past discussions\n- Priority recommendations cite relevant vault content discovered by meaning\n- \"Heads Up\" section catches connections between seemingly unrelated items\n- Focus recommendations are informed by deeper vault knowledge\n\n**If QMD is not available:** Skip silently. Steps 5.1-5.5 and 5.7 provide full context via standard methods.\n\n---\n\n### 5.7 Todoist Completion Sync (Amp Today → Amp)\n\nCheck if any tasks were completed in Todoist since the last plan:\n\n```\nUse: todoist-mcp-listTasks(filter=\"@amp & completed\")\n```\n\nFor each completed item:\n- Match to a Amp task by title\n- Update task status via Work MCP: `update_task_status(task_title=\"...\", status=\"d\")`\n- Surface what was synced:\n\n> \"📱 **Synced from Todoist:**\n> - ✅ \"Follow up with [contact]\" — marked done in Amp\"\n\n**If nothing to sync:** Skip silently.\n\n### 5.8 Email Intelligence (if Gmail connected)\n\nCheck `System\u002Fintegrations\u002Fconfig.yaml` for `google-workspace.enabled: true`.\n\nIf enabled and MCP healthy:\n1. Get unread count and priority emails from monitored labels\n2. Flag emails needing reply (> 48h since received, from key contacts in `05-Areas\u002FPeople\u002F`)\n3. Surface email threads with today's meeting attendees\n\nInclude in plan:\n\n> \"Email: [X] unread, [Y] need replies. [Z] threads with today's meeting attendees.\"\n\nIf unhealthy: skip silently (graceful degradation -- no error to user).\n\n### 5.9 Teams Intelligence (if Teams connected)\n\nCheck `System\u002Fintegrations\u002Fconfig.yaml` for `teams.enabled: true`.\n\nIf enabled and MCP healthy:\n1. Get unread messages from priority channels\n2. Surface DMs needing response\n3. Check for mentions\n\nInclude in plan:\n\n> \"**Teams:** [X] unread chats, [Y] mentions. [Z] threads with today's meeting attendees.\"\n\nIf BOTH Slack and Teams enabled:\n- Show both digests, clearly labeled: \"**Slack:** ...\" and \"**Teams:** ...\"\n- Deduplicate if the same person appears in both (merge context, label the source)\n- Present side by side in the plan output under a combined \"Chat Intelligence\" heading\n\nIf unhealthy: skip silently (graceful degradation -- no error to user).\n\n### 5.10a Mobile Capture Check (Apple Reminders)\n\nCheck for reminders created on iPhone\u002FWatch that need triage into Amp:\n\n```\nUse: pull_new_captures() from reminders MCP\n```\n\nIf items found, surface:\n\n> 📱 **Captured in Apple Reminders** (3 items):\n>\n> 1. \"Follow up with Peter about roadmap\"\n> 2. \"Look into Rovo for in-app guides\"\n> 3. \"Send Anastasia the productized offering doc\"\n>\n> **Triage these now?** I'll help assign pillars and priorities.\n\n**Triage flow:**\n- Present each item\n- Infer pillar (using existing smart pillar inference)\n- Confirm with user\n- Create task via Work MCP `process_inbox_with_dedup`\n- After task is created with a task_id, update the reminder's notes to include `^task-ID` by deleting and recreating it (or note the association)\n- Alternatively, delete the phone-captured reminder and let the new Amp task sync create a proper one\n\n**If nothing to sync:** Skip silently.\n\n### 5.10a.2 Reminders Completion Sync (Apple Reminders → Amp)\n\nCheck if any tasks were completed in Apple Reminders since the last plan:\n\n```\nUse: pull_completed_reminders() from reminders MCP\n```\n\nFor each completed item that has an Amp task ID:\n- Update task status via Work MCP: `update_task_status(task_id=\"...\", status=\"d\")`\n- Surface what was synced:\n\n> \"📱 **Synced from Apple Reminders:**\n> - ✅ \"Follow up with Nick Liffen\" — marked done in Amp\"\n\n**If nothing to sync:** Skip silently.\n\n### 5.10a.3 Todoist Capture Check (Todoist Inbox)\n\n```\nUse: todoist-mcp-listTasks(filter=\"@amp & no date\")\n```\n\nIf items found, surface:\n\n> 📱 **Captured in Todoist** (3 items):\n>\n> 1. \"Follow up with Peter about roadmap\"\n> 2. \"Look into Rovo for in-app guides\"\n> 3. \"Send Anastasia the productized offering doc\"\n>\n> **Triage these now?** I'll help assign pillars and priorities.\n\n**Triage flow:**\n- Present each item\n- Infer pillar (using existing smart pillar inference)\n- Confirm with user\n- Create task via Work MCP `process_inbox_with_dedup`\n- Complete the Todoist item via `todoist-mcp-completeTask`\n\n**If no items found:** Skip silently (no \"0 items captured\" noise).\n\n### 5.10b Standard Context Gathering\n\nAlso gather:\n- **Calendar**: Today's meetings with times and attendees\n- **Tasks**: P0, P1, started-but-not-completed, overdue\n- **Week Priorities**: This week's Top 3\n- **Work Summary**: Quarterly goals context (if enabled)\n- **People**: Context for meeting attendees\n- **Self-Learning Alerts**: Changelog updates, pending learnings\n\n---\n\n## Step 6: Synthesis\n\nCombine all gathered context into actionable recommendations:\n\n### Focus Recommendation\n\nGenerate 3 recommended focus items based on:\n- P0 tasks (highest weight)\n- Weekly priority alignment (especially lagging priorities!)\n- Meeting prep needs\n- Commitments due\n\n**The system should actively recommend, not just list:**\n\n> \"Based on your week progress and today's shape, I recommend focusing on:\n> \n> 1. **Prep for [meeting]** — Priority 2 is lagging and this meeting is critical\n> 2. **Reply to [Person]** — Commitment due today\n> 3. **Task X from Priority 1** — Keeps momentum on your shipped priority\"\n\n### Meeting Prep (Enhanced)\n\nFor each meeting, show:\n- Who's attending + People\u002F context\n- Related project status\n- Outstanding tasks with attendees\n- Suggested prep time and what to prepare\n\n### Heads Up (Enhanced)\n\nFlag potential issues:\n- Weekly priorities with no activity (midweek warning)\n- Commitments due today\n- Back-to-back meetings\n- P0 items with no time blocked\n- Deep work tasks with no suitable slot this week\n\n---\n\n## Step 6.5: Daily Plan Greeting\n\nStart each daily plan with a context-aware greeting as the FIRST line of output, before any content sections. Read the user's name from `System\u002Fuser-profile.yaml` and use it naturally (e.g., \"[Name],...\" or \"..., [Name].\"). If no name is available, omit it.\n\nChoose ONE greeting based on the most relevant context signal. **Priority order:** Day-specific > Calendar load > Task state. Never stack multiple greetings.\n\n**Day-specific:**\n- Monday → \"New week, [Name]. Here's what's carrying over and what's fresh.\"\n- Friday → \"It's Friday, [Name]. Let's close the week strong.\"\n- Wednesday\u002FThursday → \"Midweek check, [Name]. How's the week shaping up against your priorities?\"\n\n**Calendar-based (if calendar data available from Step 5.2):**\n- 4+ meetings → \"Packed schedule today, [Name]. Let's make sure you're prepped for the ones that matter.\"\n- 0-1 meetings → \"Light on meetings today. Good window for deep work.\"\n\n**Task-based (from Step 5.5 \u002F 5.10b):**\n- Overdue or rolled-over tasks from yesterday → \"A few things carried over, [Name]. Let's figure out what still matters.\"\n- No carryover (clean slate) → \"Clean slate today. What do you want to move forward?\"\n\n**Tone rules:**\n- Direct and warm. Think colleague, not cheerleader.\n- No exclamation marks. No \"Have a great day!\" or \"Let's crush it!\" energy.\n- The greeting should feel like a quick read on the day, not a motivational poster.\n\n---\n\n## Step 7: Generate Daily Plan\n\nCreate `00-Inbox\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md` (ensure the `00-Inbox\u002FPlans\u002F` folder exists first):\n\n```markdown\n---\ndate: YYYY-MM-DD\ntype: daily-plan\nintegrations_used: [calendar, tasks, people, work-intelligence]\n---\n\n# Daily Plan — {{Day}}, {{Month}} {{DD}}\n\n> {{Context-aware greeting from Step 6.5}}\n\n## TL;DR\n- {{1-2 sentence summary including week progress}}\n- {{X}} meetings today, day is {{stacked\u002Fmoderate\u002Fopen}}\n- {{Key focus area based on week priorities}}\n\n---\n\n## 📊 Week Progress (Midweek Check)\n\n**Day {{X}} of 5** — {{days_remaining}} days left this week\n\n| Priority | Status | Notes |\n|----------|--------|-------|\n| {{Priority 1}} | ✅ Complete | Finished {{day}} |\n| {{Priority 2}} | 🔄 In progress | {{X}} of {{Y}} tasks done |\n| {{Priority 3}} | ⚠️ Not started | Needs attention |\n\n**This week's focus:** {{Recommendation based on lagging priorities}}\n\n---\n\n## 📅 Today's Shape\n\n**Day type:** {{stacked\u002Fmoderate\u002Fopen}} ({{X}} meetings, {{Y}} hours)\n\n**Free blocks:**\n- {{Time range}}: {{Size}} — {{Recommended use}}\n\n**Best for:** {{Quick tasks only \u002F Medium tasks \u002F Deep work opportunity}}\n\n---\n\n## ⚡ Commitments Due Today\n\n- [ ] {{Commitment}} — from {{source}}\n- [ ] {{Commitment}} — from {{source}}\n\n---\n\n## 🎯 Today's Focus\n\n**If I only do three things today:**\n\n1. [ ] {{Focus item 1}} — {{Pillar}} *(supports Week Priority #X)*\n2. [ ] {{Focus item 2}} — {{Pillar}} *(supports Week Priority #Y)*\n3. [ ] {{Focus item 3}} — {{Pillar}}\n\n---\n\n## 📍 Meetings (with Context)\n\n### {{Time}} — {{Meeting Title}}\n\n**Attendees:** {{Names}}\n**Related project:** {{Project name}} ({{status}})\n**Outstanding with them:**\n- {{Task\u002Fcommitment}}\n\n**Prep needed:** {{What to review\u002Fprepare}}\n**Suggested prep time:** {{Block X min before}}\n\n---\n\n### {{Time}} — {{Meeting Title}}\n\n[Repeat for each meeting]\n\n---\n\n## 📋 Task Scheduling\n\n| Task | Effort | Suggested Slot | Reason |\n|------|--------|----------------|--------|\n| {{Task}} | Deep work | {{Day\u002Ftime}} | {{Reason}} |\n| {{Task}} | Medium | {{Day\u002Ftime}} | {{Reason}} |\n| {{Task}} | Quick | Between meetings | Batch these |\n\n{{If deep work capacity warning}}\n> ⚠️ You have {{X}} deep work tasks but only {{Y}} suitable slots this week. Consider protecting time or deferring.\n\n---\n\n## ⚠️ Heads Up\n\n- {{Warning about lagging weekly priority}}\n- {{Commitment due today}}\n- {{Back-to-back meetings}}\n- {{Other flags}}\n\n---\n\n*Generated: {{timestamp}}*\n*Week progress: {{X}}\u002F{{Y}} priorities on track*\n```\n\n---\n\n## Step 7.5: Push Focus Tasks to Apple Reminders\n\nAfter generating the plan, push today's P0 and P1 focus tasks to Apple Reminders for iPhone\u002FWatch visibility:\n\n1. **Push today's focus items:**\n   For each P0\u002FP1 task in today's focus:\n   ```\n   Use: sync_tasks_to_reminders(tasks=[\n       {\"title\": \"Task title\", \"task_id\": \"task-YYYYMMDD-XXX\", \"priority\": \"high\", \"notes\": \"From daily plan focus\", \"due_date\": \"YYYY-MM-DD\"}\n   ]) from reminders MCP\n   ```\n   Priority mapping: P0\u002FP1 → high, P2 → medium, P3 → low\n\n2. **Confirm silently:**\n   > \"📱 Pushed 3 focus tasks to Apple Reminders (syncs to iPhone\u002FWatch)\"\n\n**If Reminders MCP unavailable:** Skip silently.\n\n---\n\n## Step 7.5b: Push Focus Tasks to Todoist (if configured)\n\nAfter generating the plan, push today's P0 and P1 focus tasks to Todoist for mobile access:\n\n1. **Push today's focus items:**\n   For each P0\u002FP1 task in today's focus:\n   ```\n   Use: todoist-mcp-createTask(\n       content=\"Task title\",\n       description=\"From Amp daily plan\",\n       dueDate=\"YYYY-MM-DD\",\n       labels=[\"amp\"]\n   )\n   ```\n\n2. **Confirm silently:**\n   > \"📱 Pushed 3 focus tasks to Todoist\"\n\n**If Todoist MCP unavailable:** Skip silently.\n\n---\n\n## Step 7.6: Create Today's Drop Zone\n\nAfter generating the daily plan, ensure today's drop zone document exists:\n\n1. Check if `00-Inbox\u002FDrop_Zone\u002FYYYY-MM-DD - Drop Zone.md` exists (also check legacy `00-Inbox\u002FDrop_Zone\u002FYYYY-MM-DD-Drop-Zone.md`)\n2. **If neither exists**, create it with this template:\n\n```markdown\n# Drop Zone — YYYY-MM-DD\n\nPaste screenshots, Slack messages, links, quick notes here.\nRun `\u002Fcapture` to have Amp process and route these items.\n\n---\n\n```\n\n3. Open the drop zone in Obsidian:\n\n```bash\nopen \"obsidian:\u002F\u002Fopen?vault=amp&file=00-Inbox%2FDrop_Zone%2FYYYY-MM-DD%20-%20Drop%20Zone\"\n```\n\n4. **If it already exists**, skip creation but still open it in Obsidian.\n\n5. Append this line to the daily plan output (after the plan content, before the generated timestamp):\n\n> 📋 Drop zone ready — paste screenshots, links, and notes in Obsidian. Run `\u002Fcapture` when you want me to process them.\n\n---\n\n## Step 7.7: Milestone Check\n\nAfter generating the plan, check for milestone thresholds. Show ONE milestone max per session (pick the most impressive one).\n\n**Data sources:**\n1. Read `System\u002Fusage_log.md` for feature usage and tracking metadata (e.g., `First daily plan` date)\n2. Count vault files: `find . -name \"*.md\" -not -path \".\u002Fnode_modules\u002F*\" | wc -l`\n3. Count completed tasks in `03-Tasks\u002FTasks.md` (lines matching `- [x]`)\n4. Count meeting files in `00-Inbox\u002FMeetings\u002F`\n5. Count person pages in `05-Areas\u002FPeople\u002F`\n6. Calculate daily plan streak from `00-Inbox\u002FPlans\u002F` and `07-Archives\u002FPlans\u002F` (consecutive days with a plan file in either location)\n\n**Thresholds:**\n- Daily plan streak: 7, 14, 30, 60, 90 consecutive days\n- Tasks completed: 25, 50, 100, 200, 500 lifetime\n- Meetings processed: 10, 25, 50, 100\n- Person pages: 10, 25, 50\n- Vault notes: 100, 200, 500\n\n**Format:** Single line at the very end of the plan output, not blocking:\n- \"📈 14 days of daily plans. The system is compounding.\"\n- \"🎯 50 tasks completed this quarter.\"\n- \"Your vault just crossed 200 notes.\"\n\n**Tone:** Observational, not celebratory. Think \"noting momentum\" not \"throwing a party.\"\n\n**Rules:**\n- Only show when a NEW threshold is crossed (not every day)\n- Max one milestone per session\n- If no threshold crossed, show nothing (no filler)\n- Check `System\u002Fusage_log.md` for a `## Milestones Shown` section. If the threshold was already shown there, skip it.\n- After showing a milestone, append it to `System\u002Fusage_log.md` under `## Milestones Shown`:\n  ```\n  - YYYY-MM-DD: [threshold name] ([value])\n  ```\n\n---\n\n## Step 8: Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark daily planning as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `daily_plan_completed` and properties:\n- `meetings_count`: number of meetings today\n- `tasks_surfaced`: number of tasks shown\n- `priorities_count`: number of priorities\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n\n---\n\n## Graceful Degradation\n\nThe plan works at multiple levels:\n\n### Fresh Vault (First Day)\nIf the vault is less than 1 day old OR there are no tasks, no meetings, and no weekly priorities:\n- Acknowledge it: \"Your vault is brand new, so today's plan is lightweight. It will get richer as you add data.\"\n- Suggest concrete next steps instead of showing empty sections:\n  1. Create 2-3 tasks: \"What are you working on today?\" and create them via Work MCP\n  2. Set weekly priorities: \"Run `\u002Fweek-plan` to set this week's focus\"\n  3. Connect your calendar: remind them of the choice they made during onboarding\n- Still generate the daily plan file, but fill focus items with the setup tasks above\n\n### Full Context (All MCPs available)\n- Complete week progress, meeting intelligence, scheduling suggestions\n- Maximum \"surprise and delight\"\n\n### Partial Context (Work MCP only)\n- Week progress and task scheduling\n- No meeting context (prompt user to add manually)\n\n### Minimal Context (No MCPs)\n- Interactive flow asking about priorities\n- Basic daily note\n\n---\n\n## MCP Dependencies (Updated)\n\n| Integration | MCP Server | Tools Used |\n|-------------|------------|------------|\n| Calendar | calendar-mcp | `calendar_get_today`, `calendar_get_events_with_attendees` |\n| Apple Reminders | reminders-mcp | `sync_tasks_to_reminders`, `pull_completed_reminders`, `pull_new_captures`, `complete_reminder_by_task_id` |\n| Todoist | todoist-mcp | `listTasks`, `createTask`, `completeTask` |\n| Work | work-mcp | `list_tasks`, `get_week_progress`, `get_meeting_context`, `get_commitments_due`, `analyze_calendar_capacity`, `suggest_task_scheduling` |\n| Improvements | amp-improvements-mcp | `synthesize_changelog`, `synthesize_learnings`, `list_ideas` |\n| Google Workspace | google-workspace-mcp | Gmail query, email search (if enabled) |\n| Teams | teams-mcp | `teams_list_chats`, `teams_search_messages`, `teams_health_check` (if enabled) |","## Purpose\n\nGenerate your daily plan with full context awareness. Automatically gathers information from your calendar, tasks, meetings, relationships, and weekly progress to create a focused plan with genuine situational awareness.\n\n## Usage\n\n- `\u002Fdaily-plan` — Create today's daily plan\n- `\u002Fdaily-plan tomorrow` — Plan for tomorrow (evening planning)\n- `\u002Fdaily-plan --setup` — Re-run integration setup\n\n**Batch limit:** Include at most 20 calendar events and 20 tasks in a single plan. Summarize overflow items as a count.\n\n---\n\n## Tone Calibration\n\nBefore executing this command, read `System\u002Fuser-profile.yaml` → `communication` section and adapt tone accordingly (see CLAUDE.md → \"Communication Adaptation\").\n\n---\n\n## Step 0: Demo Mode Check\n\nBefore anything else, check if demo mode is active:\n\n1. Read `System\u002Fuser-profile.yaml`\n2. Check `demo_mode` value\n3. **If `demo_mode: true`:**\n   - Display banner: \"Demo Mode Active — Using sample data from System\u002FDemo\u002F\"\n   - Use demo paths and skip live integrations\n4. **If `demo_mode: false`:** Proceed normally\n\n---\n\n## Step 0.5: Prerequisite Check — Calendar\n\nBefore generating the plan, check if calendar integration is configured:\n- Look for a `calendar_integration` key in `System\u002Fuser-profile.yaml`\n- OR check if calendar MCP tools are available (e.g., `calendar_get_today`)\n\n**If calendar is NOT configured**, add this note at the start of the plan output (before the greeting):\n\n> 💡 **Calendar integration available.** Your daily plan can include meetings and prep suggestions. Options:\n> - **Apple Calendar** (direct) — Fast, uses AppleScript\n> - **Apple Calendar via EventKit** — More reliable, needs permissions\n> - **Google Calendar** — For Google Workspace users\n>\n> Run `\u002Fcalendar-setup` to connect.\n\n**If calendar IS configured**, skip this note entirely. This hint is informational and does not block plan generation.\n\n---\n\n## Step 1: Background Checks (Silent)\n\nRun these silently without user-facing output:\n\n1. **Update check**: `check_for_updates(force=False)` - store notification if available\n2. **Self-learning checks**: Run changelog and learning review scripts if due\n3. **Search index refresh**: Run `qmd update && qmd embed` to refresh vault search index with any overnight changes (meetings processed, files edited, etc.). If `qmd` is not installed, skip silently.\n4. **People index refresh**: Call `build_people_index` from Work MCP. This keeps the People Directory current so person lookups throughout the day are fast. Takes \u003C2 seconds.\n5. **Innovation synthesis** (silent): Call `synthesize_changelog()` and `synthesize_learnings()` from Improvements MCP. These run in background and populate the backlog — results are surfaced in Step 1.5 below.\n6. **Granola migration check** (silent): Run `node .scripts\u002Fmeeting-intel\u002Fcheck-granola-migration.cjs 2>\u002Fdev\u002Fnull || echo '{\"status\":\"not_applicable\"}'`. If status is `migration_available`, store this fact and append a brief note at the END of the daily plan output (after all other sections): *\"Granola now syncs phone recordings too. Run `\u002Fprocess-meetings` to set it up.\"* If the script does not exist or returns any other status, skip silently. Never interrupt the planning flow for this check.\n\n---\n\n## Step 1.5: Innovation Spotlight (Concierge)\n\nAfter background checks complete, check for noteworthy backlog activity:\n\n1. Call `list_ideas(status=\"active\", min_score=70)` from Improvements MCP\n2. Check `System\u002F.synthesis-state.json` for recent synthesis activity (last 7 days)\n3. If there are AI-authored or recently enriched ideas, pick the most impactful one\n\n**Surface as a brief spotlight in the plan output (1-2 lines max):**\n\n> **Innovation Spotlight:** Claude Code shipped native memory (v2.1.32) — this could simplify idea-006 (Session Memory MCP). Run `\u002Famp-improve idea-006` to explore.\n\n**Rules:**\n- Show at most 1 spotlight per daily plan (don't overwhelm)\n- Rotate through ideas — don't show the same one twice in a row\n- Only show if there's genuine \"Why Now?\" urgency (new evidence in last 7 days)\n- If no recent synthesis activity, skip this section entirely\n- Never block the plan for this — it's a helpful aside, not a gate\n\n---\n\n## Step 2: Morning Journal Check (If Enabled)\n\nIf `journaling.morning: true` in user-profile.yaml, check for today's morning journal and prompt if missing.\n\n---\n\n## Step 3: Monday Weekly Planning Gate\n\nIf today is Monday and week isn't planned, offer to run `\u002Fweek-plan` first.\n\n---\n\n## Step 4: Yesterday's Review Check (Soft Gate)\n\nCheck for yesterday's review and extract context (open loops, tomorrow's focus, blocked items).\n\n---\n\n## Step 5: Context Gathering (ENHANCED)\n\nGather context from all available sources. **This is where the magic happens.**\n\n### 5.1 Midweek Progress Check (NEW)\n\n```\nUse: get_week_progress()\n```\n\nThis is critical for genuine situational awareness. Extract:\n- Day of week and days remaining\n- Weekly priority status (complete \u002F in_progress \u002F not_started)\n- Warnings for priorities with no activity\n\n**Surface this prominently:**\n\n> \"It's **Wednesday**. Here's where you are on this week's priorities:\n> \n> 1. ✅ **Ship pricing page** — Complete (finished Monday)\n> 2. 🔄 **Review proposal** — In progress (2 of 5 tasks done)\n> 3. ⚠️ **Customer interviews** — Not started (no activity yet)\n> \n> You have 2 days left this week. Priority 3 needs attention.\"\n\n### 5.2 Calendar Capacity Analysis (NEW)\n\n```\nUse: analyze_calendar_capacity(days_ahead=1, events=[...from calendar MCP...])\n```\n\nUnderstand the *shape* of today:\n\n- **Day type**: stacked \u002F moderate \u002F open\n- **Meeting count and hours**\n- **Free blocks available**\n- **Recommendation**: What kind of work fits today\n\n**Surface this:**\n\n> \"📅 **Today's shape:** Moderate (4 meetings, 3 hours total)\n> \n> **Free blocks:**\n> - 8:00-9:30 AM (90 min) — Morning focus time\n> - 2:00-4:00 PM (120 min) — Afternoon block\n> \n> **Recommendation:** Good for medium tasks and meeting prep. Deep work fits the 2-4pm block.\"\n\n### 5.3 Meeting Intelligence (NEW)\n\nFor each meeting today:\n\n```\nUse: get_meeting_context(meeting_title=\"...\", attendees=[...])\n```\n\nGet genuine context, not just attendee names:\n- **Related project**: What project is this connected to?\n- **Project status**: What's outstanding? What's blocked?\n- **Outstanding tasks with attendees**: What do you owe them? What do they owe you?\n- **Prep suggestions**: What should you review before this meeting?\n\n**Surface this with surprise and delight:**\n\n> \"📍 **Meeting: [Meeting Title]** (2pm with [Attendee 1], [Attendee 2])\n> \n> **Related project:** [Project Name]\n> - Status: On track, but [section] still in draft\n> - Outstanding: You owe [Attendee 1] the [deliverable]\n> \n> **Prep suggestion:** Review [relevant doc], prepare [talking points]. Block 30 min before this meeting?\"\n\n### 5.4 Commitment Tracking (NEW)\n\n```\nUse: get_commitments_due(date_range=\"today\")\n```\n\nSurface things you said you'd do:\n\n> \"⚡ **Commitments due today:**\n> \n> - You told [Person] you'd get back to them by Wednesday (from Monday 1:1)\n> - Follow up on [deliverable] (from [meeting name])\"\n\n### 5.5 Task Scheduling Suggestions (NEW)\n\n```\nUse: suggest_task_scheduling(include_all_tasks=False, calendar_events=[...])\n```\n\nMatch tasks to available time based on effort classification:\n\n> \"📋 **Scheduling suggestions:**\n> \n> | Task | Effort | Suggested Time |\n> |------|--------|----------------|\n> | Write Q1 strategy doc | Deep work (2-3h) | Tomorrow (you have a 3h morning block) |\n> | Review [Person]'s proposal | Medium (1h) | Today 2-3pm (before [meeting]) |\n> | Reply to [Person] | Quick (15min) | Between meetings |\n> \n> ⚠️ **Heads up:** You have 2 deep work tasks but today's too fragmented. Consider protecting tomorrow morning.\"\n\n### 5.6 Semantic Context Enrichment (if QMD available)\n\n**This step runs automatically when QMD is installed via `\u002Fenable-semantic-search`.** It adds a semantic search layer on top of the standard context gathering to surface connections that keyword search misses.\n\nCheck if QMD MCP tools are available by calling `qmd_status`. **If available:**\n\n1. **For each meeting today**, run:\n   ```\n   qmd_search(query=\"[meeting topic] [attendee names]\", limit=3)\n   ```\n   Surface: past discussions, related decisions, relevant commitments that share **meaning** but not keywords with this meeting. Example: a meeting about \"customer onboarding\" finds notes about \"activation rates\" and \"time to value\".\n\n2. **For each weekly priority that's lagging**, run:\n   ```\n   qmd_search(query=\"[priority description]\", limit=3)\n   ```\n   Surface: vault content that advances or relates to this priority but wouldn't appear in a keyword search. Especially useful for finding forgotten context about stalled work.\n\n3. **Cross-topic connection scan:**\n   ```\n   qmd_search(query=\"[today's key themes combined]\", limit=5)\n   ```\n   Surface: unexpected connections between today's meetings, tasks, and priorities. This is where semantic search shines — finding that a 2pm customer call relates to a PRD you wrote last month using completely different terminology.\n\n4. **Merge with existing context** — only add genuinely new insights. Don't duplicate what Steps 5.1-5.5 already found. Mark semantic results with their source so the plan output can distinguish them.\n\n**What this enables in the plan output:**\n- Meeting context sections include \"**Also relevant:**\" with thematically related past discussions\n- Priority recommendations cite relevant vault content discovered by meaning\n- \"Heads Up\" section catches connections between seemingly unrelated items\n- Focus recommendations are informed by deeper vault knowledge\n\n**If QMD is not available:** Skip silently. Steps 5.1-5.5 and 5.7 provide full context via standard methods.\n\n---\n\n### 5.7 Todoist Completion Sync (Amp Today → Amp)\n\nCheck if any tasks were completed in Todoist since the last plan:\n\n```\nUse: todoist-mcp-listTasks(filter=\"@amp & completed\")\n```\n\nFor each completed item:\n- Match to a Amp task by title\n- Update task status via Work MCP: `update_task_status(task_title=\"...\", status=\"d\")`\n- Surface what was synced:\n\n> \"📱 **Synced from Todoist:**\n> - ✅ \"Follow up with [contact]\" — marked done in Amp\"\n\n**If nothing to sync:** Skip silently.\n\n### 5.8 Email Intelligence (if Gmail connected)\n\nCheck `System\u002Fintegrations\u002Fconfig.yaml` for `google-workspace.enabled: true`.\n\nIf enabled and MCP healthy:\n1. Get unread count and priority emails from monitored labels\n2. Flag emails needing reply (> 48h since received, from key contacts in `05-Areas\u002FPeople\u002F`)\n3. Surface email threads with today's meeting attendees\n\nInclude in plan:\n\n> \"Email: [X] unread, [Y] need replies. [Z] threads with today's meeting attendees.\"\n\nIf unhealthy: skip silently (graceful degradation -- no error to user).\n\n### 5.9 Teams Intelligence (if Teams connected)\n\nCheck `System\u002Fintegrations\u002Fconfig.yaml` for `teams.enabled: true`.\n\nIf enabled and MCP healthy:\n1. Get unread messages from priority channels\n2. Surface DMs needing response\n3. Check for mentions\n\nInclude in plan:\n\n> \"**Teams:** [X] unread chats, [Y] mentions. [Z] threads with today's meeting attendees.\"\n\nIf BOTH Slack and Teams enabled:\n- Show both digests, clearly labeled: \"**Slack:** ...\" and \"**Teams:** ...\"\n- Deduplicate if the same person appears in both (merge context, label the source)\n- Present side by side in the plan output under a combined \"Chat Intelligence\" heading\n\nIf unhealthy: skip silently (graceful degradation -- no error to user).\n\n### 5.10a Mobile Capture Check (Apple Reminders)\n\nCheck for reminders created on iPhone\u002FWatch that need triage into Amp:\n\n```\nUse: pull_new_captures() from reminders MCP\n```\n\nIf items found, surface:\n\n> 📱 **Captured in Apple Reminders** (3 items):\n>\n> 1. \"Follow up with Peter about roadmap\"\n> 2. \"Look into Rovo for in-app guides\"\n> 3. \"Send Anastasia the productized offering doc\"\n>\n> **Triage these now?** I'll help assign pillars and priorities.\n\n**Triage flow:**\n- Present each item\n- Infer pillar (using existing smart pillar inference)\n- Confirm with user\n- Create task via Work MCP `process_inbox_with_dedup`\n- After task is created with a task_id, update the reminder's notes to include `^task-ID` by deleting and recreating it (or note the association)\n- Alternatively, delete the phone-captured reminder and let the new Amp task sync create a proper one\n\n**If nothing to sync:** Skip silently.\n\n### 5.10a.2 Reminders Completion Sync (Apple Reminders → Amp)\n\nCheck if any tasks were completed in Apple Reminders since the last plan:\n\n```\nUse: pull_completed_reminders() from reminders MCP\n```\n\nFor each completed item that has an Amp task ID:\n- Update task status via Work MCP: `update_task_status(task_id=\"...\", status=\"d\")`\n- Surface what was synced:\n\n> \"📱 **Synced from Apple Reminders:**\n> - ✅ \"Follow up with Nick Liffen\" — marked done in Amp\"\n\n**If nothing to sync:** Skip silently.\n\n### 5.10a.3 Todoist Capture Check (Todoist Inbox)\n\n```\nUse: todoist-mcp-listTasks(filter=\"@amp & no date\")\n```\n\nIf items found, surface:\n\n> 📱 **Captured in Todoist** (3 items):\n>\n> 1. \"Follow up with Peter about roadmap\"\n> 2. \"Look into Rovo for in-app guides\"\n> 3. \"Send Anastasia the productized offering doc\"\n>\n> **Triage these now?** I'll help assign pillars and priorities.\n\n**Triage flow:**\n- Present each item\n- Infer pillar (using existing smart pillar inference)\n- Confirm with user\n- Create task via Work MCP `process_inbox_with_dedup`\n- Complete the Todoist item via `todoist-mcp-completeTask`\n\n**If no items found:** Skip silently (no \"0 items captured\" noise).\n\n### 5.10b Standard Context Gathering\n\nAlso gather:\n- **Calendar**: Today's meetings with times and attendees\n- **Tasks**: P0, P1, started-but-not-completed, overdue\n- **Week Priorities**: This week's Top 3\n- **Work Summary**: Quarterly goals context (if enabled)\n- **People**: Context for meeting attendees\n- **Self-Learning Alerts**: Changelog updates, pending learnings\n\n---\n\n## Step 6: Synthesis\n\nCombine all gathered context into actionable recommendations:\n\n### Focus Recommendation\n\nGenerate 3 recommended focus items based on:\n- P0 tasks (highest weight)\n- Weekly priority alignment (especially lagging priorities!)\n- Meeting prep needs\n- Commitments due\n\n**The system should actively recommend, not just list:**\n\n> \"Based on your week progress and today's shape, I recommend focusing on:\n> \n> 1. **Prep for [meeting]** — Priority 2 is lagging and this meeting is critical\n> 2. **Reply to [Person]** — Commitment due today\n> 3. **Task X from Priority 1** — Keeps momentum on your shipped priority\"\n\n### Meeting Prep (Enhanced)\n\nFor each meeting, show:\n- Who's attending + People\u002F context\n- Related project status\n- Outstanding tasks with attendees\n- Suggested prep time and what to prepare\n\n### Heads Up (Enhanced)\n\nFlag potential issues:\n- Weekly priorities with no activity (midweek warning)\n- Commitments due today\n- Back-to-back meetings\n- P0 items with no time blocked\n- Deep work tasks with no suitable slot this week\n\n---\n\n## Step 6.5: Daily Plan Greeting\n\nStart each daily plan with a context-aware greeting as the FIRST line of output, before any content sections. Read the user's name from `System\u002Fuser-profile.yaml` and use it naturally (e.g., \"[Name],...\" or \"..., [Name].\"). If no name is available, omit it.\n\nChoose ONE greeting based on the most relevant context signal. **Priority order:** Day-specific > Calendar load > Task state. Never stack multiple greetings.\n\n**Day-specific:**\n- Monday → \"New week, [Name]. Here's what's carrying over and what's fresh.\"\n- Friday → \"It's Friday, [Name]. Let's close the week strong.\"\n- Wednesday\u002FThursday → \"Midweek check, [Name]. How's the week shaping up against your priorities?\"\n\n**Calendar-based (if calendar data available from Step 5.2):**\n- 4+ meetings → \"Packed schedule today, [Name]. Let's make sure you're prepped for the ones that matter.\"\n- 0-1 meetings → \"Light on meetings today. Good window for deep work.\"\n\n**Task-based (from Step 5.5 \u002F 5.10b):**\n- Overdue or rolled-over tasks from yesterday → \"A few things carried over, [Name]. Let's figure out what still matters.\"\n- No carryover (clean slate) → \"Clean slate today. What do you want to move forward?\"\n\n**Tone rules:**\n- Direct and warm. Think colleague, not cheerleader.\n- No exclamation marks. No \"Have a great day!\" or \"Let's crush it!\" energy.\n- The greeting should feel like a quick read on the day, not a motivational poster.\n\n---\n\n## Step 7: Generate Daily Plan\n\nCreate `00-Inbox\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md` (ensure the `00-Inbox\u002FPlans\u002F` folder exists first):\n\n```markdown\n---\ndate: YYYY-MM-DD\ntype: daily-plan\nintegrations_used: [calendar, tasks, people, work-intelligence]\n---\n\n# Daily Plan — {{Day}}, {{Month}} {{DD}}\n\n> {{Context-aware greeting from Step 6.5}}\n\n## TL;DR\n- {{1-2 sentence summary including week progress}}\n- {{X}} meetings today, day is {{stacked\u002Fmoderate\u002Fopen}}\n- {{Key focus area based on week priorities}}\n\n---\n\n## 📊 Week Progress (Midweek Check)\n\n**Day {{X}} of 5** — {{days_remaining}} days left this week\n\n| Priority | Status | Notes |\n|----------|--------|-------|\n| {{Priority 1}} | ✅ Complete | Finished {{day}} |\n| {{Priority 2}} | 🔄 In progress | {{X}} of {{Y}} tasks done |\n| {{Priority 3}} | ⚠️ Not started | Needs attention |\n\n**This week's focus:** {{Recommendation based on lagging priorities}}\n\n---\n\n## 📅 Today's Shape\n\n**Day type:** {{stacked\u002Fmoderate\u002Fopen}} ({{X}} meetings, {{Y}} hours)\n\n**Free blocks:**\n- {{Time range}}: {{Size}} — {{Recommended use}}\n\n**Best for:** {{Quick tasks only \u002F Medium tasks \u002F Deep work opportunity}}\n\n---\n\n## ⚡ Commitments Due Today\n\n- [ ] {{Commitment}} — from {{source}}\n- [ ] {{Commitment}} — from {{source}}\n\n---\n\n## 🎯 Today's Focus\n\n**If I only do three things today:**\n\n1. [ ] {{Focus item 1}} — {{Pillar}} *(supports Week Priority #X)*\n2. [ ] {{Focus item 2}} — {{Pillar}} *(supports Week Priority #Y)*\n3. [ ] {{Focus item 3}} — {{Pillar}}\n\n---\n\n## 📍 Meetings (with Context)\n\n### {{Time}} — {{Meeting Title}}\n\n**Attendees:** {{Names}}\n**Related project:** {{Project name}} ({{status}})\n**Outstanding with them:**\n- {{Task\u002Fcommitment}}\n\n**Prep needed:** {{What to review\u002Fprepare}}\n**Suggested prep time:** {{Block X min before}}\n\n---\n\n### {{Time}} — {{Meeting Title}}\n\n[Repeat for each meeting]\n\n---\n\n## 📋 Task Scheduling\n\n| Task | Effort | Suggested Slot | Reason |\n|------|--------|----------------|--------|\n| {{Task}} | Deep work | {{Day\u002Ftime}} | {{Reason}} |\n| {{Task}} | Medium | {{Day\u002Ftime}} | {{Reason}} |\n| {{Task}} | Quick | Between meetings | Batch these |\n\n{{If deep work capacity warning}}\n> ⚠️ You have {{X}} deep work tasks but only {{Y}} suitable slots this week. Consider protecting time or deferring.\n\n---\n\n## ⚠️ Heads Up\n\n- {{Warning about lagging weekly priority}}\n- {{Commitment due today}}\n- {{Back-to-back meetings}}\n- {{Other flags}}\n\n---\n\n*Generated: {{timestamp}}*\n*Week progress: {{X}}\u002F{{Y}} priorities on track*\n```\n\n---\n\n## Step 7.5: Push Focus Tasks to Apple Reminders\n\nAfter generating the plan, push today's P0 and P1 focus tasks to Apple Reminders for iPhone\u002FWatch visibility:\n\n1. **Push today's focus items:**\n   For each P0\u002FP1 task in today's focus:\n   ```\n   Use: sync_tasks_to_reminders(tasks=[\n       {\"title\": \"Task title\", \"task_id\": \"task-YYYYMMDD-XXX\", \"priority\": \"high\", \"notes\": \"From daily plan focus\", \"due_date\": \"YYYY-MM-DD\"}\n   ]) from reminders MCP\n   ```\n   Priority mapping: P0\u002FP1 → high, P2 → medium, P3 → low\n\n2. **Confirm silently:**\n   > \"📱 Pushed 3 focus tasks to Apple Reminders (syncs to iPhone\u002FWatch)\"\n\n**If Reminders MCP unavailable:** Skip silently.\n\n---\n\n## Step 7.5b: Push Focus Tasks to Todoist (if configured)\n\nAfter generating the plan, push today's P0 and P1 focus tasks to Todoist for mobile access:\n\n1. **Push today's focus items:**\n   For each P0\u002FP1 task in today's focus:\n   ```\n   Use: todoist-mcp-createTask(\n       content=\"Task title\",\n       description=\"From Amp daily plan\",\n       dueDate=\"YYYY-MM-DD\",\n       labels=[\"amp\"]\n   )\n   ```\n\n2. **Confirm silently:**\n   > \"📱 Pushed 3 focus tasks to Todoist\"\n\n**If Todoist MCP unavailable:** Skip silently.\n\n---\n\n## Step 7.6: Create Today's Drop Zone\n\nAfter generating the daily plan, ensure today's drop zone document exists:\n\n1. Check if `00-Inbox\u002FDrop_Zone\u002FYYYY-MM-DD - Drop Zone.md` exists (also check legacy `00-Inbox\u002FDrop_Zone\u002FYYYY-MM-DD-Drop-Zone.md`)\n2. **If neither exists**, create it with this template:\n\n```markdown\n# Drop Zone — YYYY-MM-DD\n\nPaste screenshots, Slack messages, links, quick notes here.\nRun `\u002Fcapture` to have Amp process and route these items.\n\n---\n\n```\n\n3. Open the drop zone in Obsidian:\n\n```bash\nopen \"obsidian:\u002F\u002Fopen?vault=amp&file=00-Inbox%2FDrop_Zone%2FYYYY-MM-DD%20-%20Drop%20Zone\"\n```\n\n4. **If it already exists**, skip creation but still open it in Obsidian.\n\n5. Append this line to the daily plan output (after the plan content, before the generated timestamp):\n\n> 📋 Drop zone ready — paste screenshots, links, and notes in Obsidian. Run `\u002Fcapture` when you want me to process them.\n\n---\n\n## Step 7.7: Milestone Check\n\nAfter generating the plan, check for milestone thresholds. Show ONE milestone max per session (pick the most impressive one).\n\n**Data sources:**\n1. Read `System\u002Fusage_log.md` for feature usage and tracking metadata (e.g., `First daily plan` date)\n2. Count vault files: `find . -name \"*.md\" -not -path \".\u002Fnode_modules\u002F*\" | wc -l`\n3. Count completed tasks in `03-Tasks\u002FTasks.md` (lines matching `- [x]`)\n4. Count meeting files in `00-Inbox\u002FMeetings\u002F`\n5. Count person pages in `05-Areas\u002FPeople\u002F`\n6. Calculate daily plan streak from `00-Inbox\u002FPlans\u002F` and `07-Archives\u002FPlans\u002F` (consecutive days with a plan file in either location)\n\n**Thresholds:**\n- Daily plan streak: 7, 14, 30, 60, 90 consecutive days\n- Tasks completed: 25, 50, 100, 200, 500 lifetime\n- Meetings processed: 10, 25, 50, 100\n- Person pages: 10, 25, 50\n- Vault notes: 100, 200, 500\n\n**Format:** Single line at the very end of the plan output, not blocking:\n- \"📈 14 days of daily plans. The system is compounding.\"\n- \"🎯 50 tasks completed this quarter.\"\n- \"Your vault just crossed 200 notes.\"\n\n**Tone:** Observational, not celebratory. Think \"noting momentum\" not \"throwing a party.\"\n\n**Rules:**\n- Only show when a NEW threshold is crossed (not every day)\n- Max one milestone per session\n- If no threshold crossed, show nothing (no filler)\n- Check `System\u002Fusage_log.md` for a `## Milestones Shown` section. If the threshold was already shown there, skip it.\n- After showing a milestone, append it to `System\u002Fusage_log.md` under `## Milestones Shown`:\n  ```\n  - YYYY-MM-DD: [threshold name] ([value])\n  ```\n\n---\n\n## Step 8: Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark daily planning as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `daily_plan_completed` and properties:\n- `meetings_count`: number of meetings today\n- `tasks_surfaced`: number of tasks shown\n- `priorities_count`: number of priorities\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n\n---\n\n## Graceful Degradation\n\nThe plan works at multiple levels:\n\n### Fresh Vault (First Day)\nIf the vault is less than 1 day old OR there are no tasks, no meetings, and no weekly priorities:\n- Acknowledge it: \"Your vault is brand new, so today's plan is lightweight. It will get richer as you add data.\"\n- Suggest concrete next steps instead of showing empty sections:\n  1. Create 2-3 tasks: \"What are you working on today?\" and create them via Work MCP\n  2. Set weekly priorities: \"Run `\u002Fweek-plan` to set this week's focus\"\n  3. Connect your calendar: remind them of the choice they made during onboarding\n- Still generate the daily plan file, but fill focus items with the setup tasks above\n\n### Full Context (All MCPs available)\n- Complete week progress, meeting intelligence, scheduling suggestions\n- Maximum \"surprise and delight\"\n\n### Partial Context (Work MCP only)\n- Week progress and task scheduling\n- No meeting context (prompt user to add manually)\n\n### Minimal Context (No MCPs)\n- Interactive flow asking about priorities\n- Basic daily note\n\n---\n\n## MCP Dependencies (Updated)\n\n| Integration | MCP Server | Tools Used |\n|-------------|------------|------------|\n| Calendar | calendar-mcp | `calendar_get_today`, `calendar_get_events_with_attendees` |\n| Apple Reminders | reminders-mcp | `sync_tasks_to_reminders`, `pull_completed_reminders`, `pull_new_captures`, `complete_reminder_by_task_id` |\n| Todoist | todoist-mcp | `listTasks`, `createTask`, `completeTask` |\n| Work | work-mcp | `list_tasks`, `get_week_progress`, `get_meeting_context`, `get_commitments_due`, `analyze_calendar_capacity`, `suggest_task_scheduling` |\n| Improvements | amp-improvements-mcp | `synthesize_changelog`, `synthesize_learnings`, `list_ideas` |\n| Google Workspace | google-workspace-mcp | Gmail query, email search (if enabled) |\n| Teams | teams-mcp | `teams_list_chats`, `teams_search_messages`, `teams_health_check` (if enabled) |",{"name":5,"context":24,"description":7},"fork","main","6a447b9ff35eed7bda9e12399bcd373dd31e0a53",".claude\u002Fskills\u002Fdaily-plan","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp","https:\u002F\u002Fgithub.com\u002Fhemory","https:\u002F\u002Fwww.heminthehat.com\u002F","The People Developer | L&D Program Manager | Software Engineer","2026-06-09 00:20:04",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add hemory\u002Famp --skill daily-plan",{"tool":39,"command":40},"bunx","bunx skills add hemory\u002Famp --skill daily-plan",{"tool":42,"command":43},"pnpm","pnpm dlx skills add hemory\u002Famp --skill daily-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdaily-plan\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M76W5GGTP0YHZQQJ4G2ZPSZE","zoom-setup","Connect Zoom to Amp for meeting recordings, scheduling, and transcript context","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fzoom-setup\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M76W5CWR8MABE0XPZVRXFMDK","xray","Understand what just happened under the hood - learn AI by seeing it in action","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxray\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M76W582J6PD3TTXZXFA2HVQJ","week-review","Review week's progress with concrete accomplishments (not fake percentages), pattern detection, and goal tracking.","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-review\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M76W54EY8D8Y55DEPYPJ9YBV","week-plan","Set weekly priorities and plan the week ahead with intelligent suggestions based on goals, calendar shape, and task effort.","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-plan\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M76W527EJ43YXBN0CE9SRAYT","triage","Strategically route orphaned files and extract scattered tasks","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M76W4ZYRDVHZ3SS8W5WZ53Q8","trello-setup","Connect Trello to Amp for visual Kanban task sync","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftrello-setup\u002FSKILL.md",[],[]]