[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76W311G00B7HG3H2J5ECTAT":3,"skill-same:01M76W311G00B7HG3H2J5ECTAT":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},"01M76W311G00B7HG3H2J5ECTAT","daily-review",null,"End of day review with learning capture, daily plan completion tracking, and meeting follow-up surfacing.","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-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: daily-review\ndescription: End of day review with learning capture, daily plan completion tracking, and meeting follow-up surfacing.\ncontext: fork\n---\n\n## Purpose\n\nConduct an end-of-day review to capture progress, track what you actually accomplished vs. planned, surface meeting follow-ups, and set up tomorrow.\n\n## Tone Calibration\n\nRead `System\u002Fuser-profile.yaml` → `communication` section and adapt accordingly.\n\n---\n\n## Step 0: Demo Mode Check\n\nCheck `System\u002Fuser-profile.yaml` for `demo_mode`. If true, use demo paths.\n\n---\n\n## Step 1: File Discovery\n\nFind files modified TODAY:\n\n```bash\nTODAY=$(date +%Y-%m-%d)\nfind . -type f -name \"*.md\" -newermt \"$TODAY 00:00:00\" ! -newermt \"$TODAY 23:59:59\" 2>\u002Fdev\u002Fnull\n```\n\n**Critical rules:**\n1. No truncation — list all modified files\n2. Today only — use date-based filtering\n3. Verify with user — \"These are the files I found. What did you actually work on?\"\n\n---\n\n## Step 2: Gather Context\n\n### From 03-Tasks\u002FTasks.md\n- Tasks completed today (look for `✅ YYYY-MM-DD` matching today)\n- Tasks started but not finished\n\n### From Weekly Priorities\nRead `02-Week_Priorities\u002FWeek_Priorities.md` for:\n- This week's strategic focus\n- How today's work connects to weekly priorities\n\n### From Recent Meetings\nCheck `00-Inbox\u002FMeetings\u002F` for meeting notes from today.\n\n### From ScreenPipe (If Running)\n\n**Check if ScreenPipe is available:**\n```bash\ncurl -s http:\u002F\u002Flocalhost:3030\u002Fhealth | jq -r '.status' 2>\u002Fdev\u002Fnull\n```\n\nIf ScreenPipe is running, gather automatic activity context:\n\n1. **Time Audit** — Query app usage for today:\n   ```\n   Use: screenpipe_time_audit(start_time=\"YYYY-MM-DDT09:00:00\", end_time=\"YYYY-MM-DDT18:00:00\")\n   ```\n\n2. **Activity Summary** — Get narrative of what happened:\n   ```\n   Use: screenpipe_summarize(start_time=\"YYYY-MM-DDT09:00:00\", end_time=\"YYYY-MM-DDT18:00:00\")\n   ```\n\n3. **Surface to User:**\n   > \"📺 **Screen Activity Summary** (auto-captured):\n   > \n   > **Time breakdown:**\n   > - VS Code: 3.2 hours (41%)\n   > - Slack: 1.5 hours (19%)\n   > - Chrome: 2.1 hours (27%)\n   > - Zoom: 1.0 hour (13%)\n   > \n   > **Activity narrative:**\n   > [Generated summary of the day]\n   > \n   > **Context switches:** 34 (moderate)\n   > **Longest focus session:** 48 minutes\n   > \n   > Does this match your sense of the day?\"\n\nThis provides ground truth for what actually happened vs. what was remembered.\n\n### Commitment Scan (If ScreenPipe Beta Activated & Enabled & Running)\n\n**First, check beta activation:**\n```\nUse: check_beta_enabled(feature=\"screenpipe\")\n```\n\nIf beta NOT activated, skip this section entirely.\n\n**Then check if user has opted in:**\n\nRead `System\u002Fuser-profile.yaml` → `screenpipe.enabled`. If false, skip this section entirely.\n\n**If beta activated AND enabled**, scan for uncommitted asks and promises:\n\n```\nUse: scan_for_commitments(\n    start_time=\"YYYY-MM-DDT09:00:00\",\n    end_time=\"YYYY-MM-DDT18:00:00\",\n    apps=[\"Slack\", \"Gmail\", \"Teams\", \"Notion\"]\n)\n```\n\nThen get pending items:\n```\nUse: get_uncommitted_items(include_dismissed=false)\n```\n\n**Surface to user if items found:**\n\n> \"🔔 **Uncommitted Items Detected**\n>\n> ScreenPipe noticed these potential commitments today that don't have matching tasks:\n>\n> ### Inbound Asks\n>\n> **1. [Contact Name]** (Slack, 2:34 PM)\n> > \"Can you review the proposal by Friday?\"\n>\n> 📎 Matches: **[Related Project]**\n> ⏰ Deadline: Friday\n>\n> → [Create task] [Already handled] [Ignore]\n>\n> ### Outbound Promises\n>\n> **2. You → [Contact Name]** (Slack, 4:20 PM)\n> > \"I'll send over the analysis tomorrow\"\n>\n> 📎 Matches: **[Related Project]**\n> ⏰ Deadline: Tomorrow\n>\n> → [Create task] [Already handled] [Ignore]\n>\n> *2 potential commitments detected. 0 have matching tasks.*\"\n\nFor each item the user wants to create as a task:\n```\nUse: process_commitment(commitment_id=\"comm-XXXXXX-XXX\", action=\"create_task\")\nUse: create_task(title=\"...\", priority=\"P2\", pillar=\"...\", context=\"From Slack commitment\")\n```\n\nFor dismissals:\n```\nUse: process_commitment(commitment_id=\"comm-XXXXXX-XXX\", action=\"dismiss\")\n```\n\n---\n\n## Step 2.5: Semantic Context Enrichment (if QMD available)\n\n**Check if semantic search is available** by looking for `qmd` in PATH. If available, use it to map today's work to priorities and goals more intelligently.\n\n### What to search:\n\n1. **Map completed tasks to goals:** For each task completed today, search semantically:\n   ```\n   qmd query \"task description here\" --limit 3\n   ```\n   Look for connections to quarterly goals or weekly priorities that keyword matching would miss. Example: completing \"finalize stakeholder deck\" might connect to a goal about \"executive engagement strategy\" — same concept, different words.\n\n2. **Enrich meeting follow-ups:** For each meeting today, search for related past discussions:\n   ```\n   qmd query \"meeting topic\" --limit 5\n   ```\n   Surface any commitments, decisions, or context from previous meetings on the same theme.\n\n3. **Priority alignment check:** For each weekly priority, search for today's work that advanced it:\n   ```\n   qmd query \"priority title\u002Fdescription\" --limit 5\n   ```\n   Catch work that moved the needle but wasn't explicitly tagged to the priority.\n\n### How to use results:\n\n- **Only surface genuinely new connections** — if a task was already linked to a goal, don't repeat it\n- Merge insights into the Plan vs. Reality section: \"Task X also advanced Goal Y (semantic match)\"\n- Add to the Weekly Priorities Progress section if semantic search reveals hidden progress\n- If QMD is not available, skip this step silently — the review works fine without it\n\n---\n\n## Step 2.6: Reminders Completion Sync (Amp Today → Amp)\n\nCheck if tasks were completed on phone since the morning plan:\n\n```\nUse: reminders_list_completed(list_name=\"Amp Today\")\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 phone:**\n> - ✅ \"[task title]\" — marked done in Amp\"\n\nAlso check for tasks completed in Amp today that still have active Reminders:\n\n```\n# For each task completed today in Amp, check if a matching Reminder exists\nUse: reminders_find_and_complete(list_name=\"Amp Today\", title_query=\"task title\")\n```\n\nClean up completed items:\n```\nUse: reminders_clear_completed(list_name=\"Amp Today\")\n```\n\n**If nothing to sync:** Skip silently.\n\n---\n\n## Step 3: Daily Plan Completion Tracking (NEW)\n\n**Compare what you planned vs. what you did.**\n\n### 3.1 Find Today's Plan\n\nLook for today's plan in this order (use the first one found):\n1. `00-Inbox\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md` (current location)\n2. `07-Archives\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md` (archived)\n3. `07-Archives\u002FPlans\u002FYYYY-MM-DD.md` (legacy naming)\n\n### 3.2 Extract Planned Focus\n\nFrom the \"Today's Focus\" section, extract the 3 items you planned to focus on.\n\n### 3.3 Track Completion\n\nFor each planned focus item:\n- Check if it was completed (look in Tasks.md for completion timestamps)\n- Check if it was started but not finished\n- Check if it was blocked or deferred\n\n### 3.4 Count Total Throughput\n\nCount ALL tasks completed today, not just the 3 planned focus items:\n- Scan `03-Tasks\u002FTasks.md` for completion timestamps matching today's date (✅ YYYY-MM-DD)\n- Include tasks that weren't in the daily plan but got done anyway (cascading work, quick wins, unplanned items)\n- This is the \"total throughput\" number\n\n**Surface both numbers:**\n\n> \"📊 **Daily Plan Completion:**\n> \n> You planned 3 focus items this morning:\n> \n> 1. ✅ **Prep for [meeting]** — Complete\n> 2. 🔄 **Write [deliverable]** — In progress (about 60% done)\n> 3. ❌ **Reply to [Person]** — Didn't get to it\n> \n> **Plan completion:** 1 of 3 (33%)\n> **Total throughput:** 7 tasks shipped\n> \n> The gap between plan and throughput tells the story: Focus #1 cascaded into 4 follow-on tasks (launch comms, Slack post, discussion update, issue update). High-output day despite low plan completion.\"\n\n### 3.5 Track Over Time (Optional)\n\nIf tracking completion rates:\n- Update `System\u002Fmetrics\u002Fdaily-completion.md` with today's plan completion rate AND total throughput\n- Surface patterns: \"Your average plan completion this week is 53%, but average throughput is 5 tasks\u002Fday\"\n- When throughput consistently exceeds plan completion, note the pattern: \"Your planned items tend to cascade. Consider this when estimating your day.\"\n\n---\n\n## Step 4: Meeting Follow-Up Surfacing (NEW)\n\n**For each meeting you had today, surface follow-ups.**\n\n### 4.1 Identify Today's Meetings\n\nFrom calendar or meeting notes, list meetings that happened today.\n\n### 4.2 For Each Meeting, Ask:\n\n```\nUse: get_meeting_context(meeting_title=\"...\", attendees=[...])\n```\n\nThen prompt:\n\n> \"📍 **You met with [Person] today** ([Meeting Title])\n> \n> **Any follow-ups to capture?**\n> - Action items you committed to?\n> - Things they owe you?\n> - Decisions that need documentation?\n> \n> (Type your follow-ups or 'none')\"\n\n### 4.3 Create Follow-Up Tasks\n\nFor any follow-ups mentioned:\n- Add to Tasks.md with appropriate priority\n- Link to the person page\n- Add due date if mentioned\n\n---\n\n## Step 5: Progress Assessment\n\nWith user-verified information:\n- What was accomplished?\n- What progress was made against weekly priorities?\n- What got stuck or blocked?\n- What unexpected things came up?\n\n---\n\n## Step 6: Week Progress Check (Midweek Context)\n\n```\nUse: get_week_progress()\n```\n\nShow how today's work moved weekly priorities:\n\n> \"**Week Progress Update:**\n> \n> After today, you're at:\n> - Priority 1: ✅ Complete (finished today!)\n> - Priority 2: 🔄 60% (moved from 40%)\n> - Priority 3: ⚠️ Still not started\n> \n> You have 2 days left. Tomorrow should focus on Priority 3.\"\n\n---\n\n## Step 7: Auto-Extract Session Learnings\n\nScan today's conversation for learnings:\n\n1. **Mistakes or corrections** — Did something not work as expected?\n2. **Preferences mentioned** — Did you express how you like to work?\n3. **Documentation gaps** — Were there questions about how the system works?\n4. **Workflow inefficiencies** — Did any task take longer than it should?\n\nWrite to `System\u002FSession_Learnings\u002FYYYY-MM-DD.md`.\n\nThen ask: \"I captured [N] learnings from today's session. Anything else you'd like to add?\"\n\n---\n\n## Step 8: Categorize Learnings (If Applicable)\n\nCheck if any learnings should be elevated to pattern files:\n- **Recurring mistakes** → `06-Resources\u002FLearnings\u002FMistake_Patterns.md`\n- **Workflow preferences** → `06-Resources\u002FLearnings\u002FWorking_Preferences.md`\n\nGet user confirmation before adding.\n\n---\n\n## Step 9: Tomorrow's Setup\n\nBased on:\n- Incomplete items from today\n- Weekly priorities (especially lagging ones)\n- Commitments due tomorrow\n- Tomorrow's calendar shape\n\nSuggest 3 focus items for tomorrow:\n\n> \"**Suggested focus for tomorrow (Thursday):**\n> \n> 1. **Priority 3** — It's been untouched all week and you have 2 days left\n> 2. **Finish pricing proposal** — 40% left, should be quick to complete\n> 3. **Reply to Mike** — Carried from today\n> \n> Tomorrow's shape: Moderate (4 meetings). You have a 2-hour block in the afternoon.\n> \n> Does this feel right?\"\n\n---\n\n## Step 9.5: Retrospective Insight (Innovation Concierge)\n\nAt the end of the review, check if there's a relevant backlog idea to surface:\n\n1. Call `list_ideas(status=\"active\", min_score=70)` from Improvements MCP\n2. Look for ideas that connect to today's work or learnings:\n   - Did the user work on tasks related to a backlog idea?\n   - Did learnings captured today strengthen an existing idea?\n   - Is there a \"Why Now?\" idea with fresh evidence?\n3. If a relevant match exists, surface it briefly:\n\n> **Retrospective Insight:** Today's meeting processing struggles connect to idea-027 (RAG-Powered Vault Search) — semantic search could make finding meeting context much faster. Worth exploring? Run `\u002Famp-improve idea-027`.\n\n**Rules:**\n- Show at most 1 insight per review\n- Only show if genuinely connected to today's work (not random)\n- Frame as retrospective — \"based on what you just did, here's what could help\"\n- If no connection, skip entirely\n- Keep it to 1-2 lines max\n\n---\n\n## Step 10: Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark daily review as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `daily_review_completed` and properties:\n- `wins_count`\n- `learnings_count`\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n\n---\n\n## Step 11: Evening Journal (If Enabled)\n\nIf `journaling.evening: true`, prompt for evening reflection.\n\n---\n\n## Step 11.5: Archive Today's Plan\n\nMove today's daily plan from Inbox to Archives:\n\n```bash\nif [ -f \"00-Inbox\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md\" ]; then\n  mkdir -p \"07-Archives\u002FPlans\"\n  if [ -e \"07-Archives\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md\" ]; then\n    echo \"Archive already exists; not overwriting.\"\n  else\n    mv \"00-Inbox\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md\" \"07-Archives\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md\"\n  fi\nfi\n```\n\n---\n\n## Output Format\n\nCreate `07-Archives\u002FReviews\u002FYYYY-MM-DD - Daily Review.md`:\n\n```markdown\n---\ndate: YYYY-MM-DD\ntype: daily-review\nplan_completion_rate: X%\ntotal_throughput: X\n---\n\n# Daily Review — [Day], [Month] [DD], [YYYY]\n\n## 📊 Plan vs. Reality\n\n**Planned focus:**\n1. [x] [Planned item 1] — ✅ Complete\n2. [ ] [Planned item 2] — 🔄 In progress (X%)\n3. [ ] [Planned item 3] — ❌ Didn't start\n\n**Plan completion:** X of 3 (X%)\n**Total throughput:** X tasks shipped *(includes unplanned work that emerged from planned items)*\n\n**What happened:** [Brief explanation of deviations. If throughput >> plan completion, note what cascaded from the planned items.]\n\n---\n\n## ✅ Accomplished\n\n- ✓ [Completed item 1]\n- ✓ [Completed item 2]\n\n---\n\n## 🔄 Progress Made\n\n| Area | Movement |\n|------|----------|\n| [Priority 1] | [What moved forward] |\n| [Priority 2] | [What moved forward] |\n\n---\n\n## 📊 Weekly Priorities Progress\n\nAfter today:\n- **Priority 1:** [Status\u002Fprogress] — [emoji]\n- **Priority 2:** [Status\u002Fprogress] — [emoji]\n- **Priority 3:** [Status\u002Fprogress] — [emoji]\n\n**Days remaining this week:** [X]\n\n---\n\n## 📍 Meeting Follow-Ups\n\n### From [Meeting Name]\n- [ ] [Follow-up action] — due [date]\n- [ ] [Follow-up action]\n\n---\n\n## 📺 Screen Activity (Auto-Captured)\n\n**Time by App:**\n| App | Time | % |\n|-----|------|---|\n| [App 1] | Xh Xm | X% |\n| [App 2] | Xh Xm | X% |\n\n**Metrics:**\n- Context switches: [X]\n- Longest focus: [X] minutes\n- Deep work ratio: [X]%\n\n**Activity Summary:**\n[Narrative summary from ScreenPipe]\n\n---\n\n## 💡 Insights\n\n- [Key realization or connection]\n- [Important learning]\n\n---\n\n## 🚫 Blocked\u002FStuck\n\n| Item | Blocker | Status |\n|------|---------|--------|\n| [Item] | [What's blocking] | [Status] |\n\n---\n\n## ❓ Discovered Questions\n\n1. [New question that emerged]\n2. [Thing to research]\n\n---\n\n## 📅 Tomorrow's Focus\n\nBased on weekly priorities and today's carryover:\n\n1. [Priority 1 — tied to weekly focus]\n2. [Priority 2]\n3. [Priority 3]\n\n**Tomorrow's shape:** [stacked\u002Fmoderate\u002Fopen]\n\n---\n\n## 🔄 Open Loops\n\n- [ ] [Thing to remember]\n- [ ] [Person to follow up with]\n- [ ] **Awaiting:** [What you're waiting on from others]\n\n---\n\n*Generated: [timestamp]*\n*Plan completion rate: X%*\n*Total throughput: X tasks shipped*\n*Week progress: X\u002F3 priorities on track*\n```\n\n---\n\n## Step 12: Skill Quality Check (Gentle)\n\nAfter generating the review, call `get_skill_ratings(skill_name=\"daily-review\")` from Work MCP.\n\n**If 3+ ratings exist and average has dropped below 3.0 over the last 5 entries:**\nAdd one line at the end of the review output:\n> \"Your daily reviews have been averaging [X]\u002F5 lately. Common note: '[most recent note]'. Want to adjust the format?\"\n\n**If no ratings exist or average is 3.0+:** Say nothing. Don't mention ratings at all.\n\n**Then:** Run `\u002Fidentity-snapshot` silently in the background if `System\u002Fidentity-model.md` is older than 7 days (check file mtime). Don't announce this.\n\n---\n\n## MCP Dependencies\n\n| Integration | MCP Server | Tools Used |\n|-------------|------------|------------|\n| Work | work-mcp | `list_tasks`, `get_week_progress`, `get_commitments_due`, `analyze_calendar_capacity` |\n| Calendar | calendar-mcp | `calendar_get_today` |\n| Reminders | calendar-mcp | `reminders_list_completed`, `reminders_find_and_complete`, `reminders_clear_completed` |\n| Screen Activity | screenpipe-mcp | `screenpipe_time_audit`, `screenpipe_summarize`, `screenpipe_query` |\n\n### ScreenPipe Integration Notes\n\nScreenPipe provides automatic activity capture. When available:\n- Pre-fills \"what you actually did\" with ground truth data\n- Surfaces time allocation across apps\n- Identifies communication overhead vs. deep work\n- Detects context-switching patterns\n\nIf ScreenPipe is not running, skip the screen activity section gracefully.\n","## Purpose\n\nConduct an end-of-day review to capture progress, track what you actually accomplished vs. planned, surface meeting follow-ups, and set up tomorrow.\n\n## Tone Calibration\n\nRead `System\u002Fuser-profile.yaml` → `communication` section and adapt accordingly.\n\n---\n\n## Step 0: Demo Mode Check\n\nCheck `System\u002Fuser-profile.yaml` for `demo_mode`. If true, use demo paths.\n\n---\n\n## Step 1: File Discovery\n\nFind files modified TODAY:\n\n```bash\nTODAY=$(date +%Y-%m-%d)\nfind . -type f -name \"*.md\" -newermt \"$TODAY 00:00:00\" ! -newermt \"$TODAY 23:59:59\" 2>\u002Fdev\u002Fnull\n```\n\n**Critical rules:**\n1. No truncation — list all modified files\n2. Today only — use date-based filtering\n3. Verify with user — \"These are the files I found. What did you actually work on?\"\n\n---\n\n## Step 2: Gather Context\n\n### From 03-Tasks\u002FTasks.md\n- Tasks completed today (look for `✅ YYYY-MM-DD` matching today)\n- Tasks started but not finished\n\n### From Weekly Priorities\nRead `02-Week_Priorities\u002FWeek_Priorities.md` for:\n- This week's strategic focus\n- How today's work connects to weekly priorities\n\n### From Recent Meetings\nCheck `00-Inbox\u002FMeetings\u002F` for meeting notes from today.\n\n### From ScreenPipe (If Running)\n\n**Check if ScreenPipe is available:**\n```bash\ncurl -s http:\u002F\u002Flocalhost:3030\u002Fhealth | jq -r '.status' 2>\u002Fdev\u002Fnull\n```\n\nIf ScreenPipe is running, gather automatic activity context:\n\n1. **Time Audit** — Query app usage for today:\n   ```\n   Use: screenpipe_time_audit(start_time=\"YYYY-MM-DDT09:00:00\", end_time=\"YYYY-MM-DDT18:00:00\")\n   ```\n\n2. **Activity Summary** — Get narrative of what happened:\n   ```\n   Use: screenpipe_summarize(start_time=\"YYYY-MM-DDT09:00:00\", end_time=\"YYYY-MM-DDT18:00:00\")\n   ```\n\n3. **Surface to User:**\n   > \"📺 **Screen Activity Summary** (auto-captured):\n   > \n   > **Time breakdown:**\n   > - VS Code: 3.2 hours (41%)\n   > - Slack: 1.5 hours (19%)\n   > - Chrome: 2.1 hours (27%)\n   > - Zoom: 1.0 hour (13%)\n   > \n   > **Activity narrative:**\n   > [Generated summary of the day]\n   > \n   > **Context switches:** 34 (moderate)\n   > **Longest focus session:** 48 minutes\n   > \n   > Does this match your sense of the day?\"\n\nThis provides ground truth for what actually happened vs. what was remembered.\n\n### Commitment Scan (If ScreenPipe Beta Activated & Enabled & Running)\n\n**First, check beta activation:**\n```\nUse: check_beta_enabled(feature=\"screenpipe\")\n```\n\nIf beta NOT activated, skip this section entirely.\n\n**Then check if user has opted in:**\n\nRead `System\u002Fuser-profile.yaml` → `screenpipe.enabled`. If false, skip this section entirely.\n\n**If beta activated AND enabled**, scan for uncommitted asks and promises:\n\n```\nUse: scan_for_commitments(\n    start_time=\"YYYY-MM-DDT09:00:00\",\n    end_time=\"YYYY-MM-DDT18:00:00\",\n    apps=[\"Slack\", \"Gmail\", \"Teams\", \"Notion\"]\n)\n```\n\nThen get pending items:\n```\nUse: get_uncommitted_items(include_dismissed=false)\n```\n\n**Surface to user if items found:**\n\n> \"🔔 **Uncommitted Items Detected**\n>\n> ScreenPipe noticed these potential commitments today that don't have matching tasks:\n>\n> ### Inbound Asks\n>\n> **1. [Contact Name]** (Slack, 2:34 PM)\n> > \"Can you review the proposal by Friday?\"\n>\n> 📎 Matches: **[Related Project]**\n> ⏰ Deadline: Friday\n>\n> → [Create task] [Already handled] [Ignore]\n>\n> ### Outbound Promises\n>\n> **2. You → [Contact Name]** (Slack, 4:20 PM)\n> > \"I'll send over the analysis tomorrow\"\n>\n> 📎 Matches: **[Related Project]**\n> ⏰ Deadline: Tomorrow\n>\n> → [Create task] [Already handled] [Ignore]\n>\n> *2 potential commitments detected. 0 have matching tasks.*\"\n\nFor each item the user wants to create as a task:\n```\nUse: process_commitment(commitment_id=\"comm-XXXXXX-XXX\", action=\"create_task\")\nUse: create_task(title=\"...\", priority=\"P2\", pillar=\"...\", context=\"From Slack commitment\")\n```\n\nFor dismissals:\n```\nUse: process_commitment(commitment_id=\"comm-XXXXXX-XXX\", action=\"dismiss\")\n```\n\n---\n\n## Step 2.5: Semantic Context Enrichment (if QMD available)\n\n**Check if semantic search is available** by looking for `qmd` in PATH. If available, use it to map today's work to priorities and goals more intelligently.\n\n### What to search:\n\n1. **Map completed tasks to goals:** For each task completed today, search semantically:\n   ```\n   qmd query \"task description here\" --limit 3\n   ```\n   Look for connections to quarterly goals or weekly priorities that keyword matching would miss. Example: completing \"finalize stakeholder deck\" might connect to a goal about \"executive engagement strategy\" — same concept, different words.\n\n2. **Enrich meeting follow-ups:** For each meeting today, search for related past discussions:\n   ```\n   qmd query \"meeting topic\" --limit 5\n   ```\n   Surface any commitments, decisions, or context from previous meetings on the same theme.\n\n3. **Priority alignment check:** For each weekly priority, search for today's work that advanced it:\n   ```\n   qmd query \"priority title\u002Fdescription\" --limit 5\n   ```\n   Catch work that moved the needle but wasn't explicitly tagged to the priority.\n\n### How to use results:\n\n- **Only surface genuinely new connections** — if a task was already linked to a goal, don't repeat it\n- Merge insights into the Plan vs. Reality section: \"Task X also advanced Goal Y (semantic match)\"\n- Add to the Weekly Priorities Progress section if semantic search reveals hidden progress\n- If QMD is not available, skip this step silently — the review works fine without it\n\n---\n\n## Step 2.6: Reminders Completion Sync (Amp Today → Amp)\n\nCheck if tasks were completed on phone since the morning plan:\n\n```\nUse: reminders_list_completed(list_name=\"Amp Today\")\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 phone:**\n> - ✅ \"[task title]\" — marked done in Amp\"\n\nAlso check for tasks completed in Amp today that still have active Reminders:\n\n```\n# For each task completed today in Amp, check if a matching Reminder exists\nUse: reminders_find_and_complete(list_name=\"Amp Today\", title_query=\"task title\")\n```\n\nClean up completed items:\n```\nUse: reminders_clear_completed(list_name=\"Amp Today\")\n```\n\n**If nothing to sync:** Skip silently.\n\n---\n\n## Step 3: Daily Plan Completion Tracking (NEW)\n\n**Compare what you planned vs. what you did.**\n\n### 3.1 Find Today's Plan\n\nLook for today's plan in this order (use the first one found):\n1. `00-Inbox\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md` (current location)\n2. `07-Archives\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md` (archived)\n3. `07-Archives\u002FPlans\u002FYYYY-MM-DD.md` (legacy naming)\n\n### 3.2 Extract Planned Focus\n\nFrom the \"Today's Focus\" section, extract the 3 items you planned to focus on.\n\n### 3.3 Track Completion\n\nFor each planned focus item:\n- Check if it was completed (look in Tasks.md for completion timestamps)\n- Check if it was started but not finished\n- Check if it was blocked or deferred\n\n### 3.4 Count Total Throughput\n\nCount ALL tasks completed today, not just the 3 planned focus items:\n- Scan `03-Tasks\u002FTasks.md` for completion timestamps matching today's date (✅ YYYY-MM-DD)\n- Include tasks that weren't in the daily plan but got done anyway (cascading work, quick wins, unplanned items)\n- This is the \"total throughput\" number\n\n**Surface both numbers:**\n\n> \"📊 **Daily Plan Completion:**\n> \n> You planned 3 focus items this morning:\n> \n> 1. ✅ **Prep for [meeting]** — Complete\n> 2. 🔄 **Write [deliverable]** — In progress (about 60% done)\n> 3. ❌ **Reply to [Person]** — Didn't get to it\n> \n> **Plan completion:** 1 of 3 (33%)\n> **Total throughput:** 7 tasks shipped\n> \n> The gap between plan and throughput tells the story: Focus #1 cascaded into 4 follow-on tasks (launch comms, Slack post, discussion update, issue update). High-output day despite low plan completion.\"\n\n### 3.5 Track Over Time (Optional)\n\nIf tracking completion rates:\n- Update `System\u002Fmetrics\u002Fdaily-completion.md` with today's plan completion rate AND total throughput\n- Surface patterns: \"Your average plan completion this week is 53%, but average throughput is 5 tasks\u002Fday\"\n- When throughput consistently exceeds plan completion, note the pattern: \"Your planned items tend to cascade. Consider this when estimating your day.\"\n\n---\n\n## Step 4: Meeting Follow-Up Surfacing (NEW)\n\n**For each meeting you had today, surface follow-ups.**\n\n### 4.1 Identify Today's Meetings\n\nFrom calendar or meeting notes, list meetings that happened today.\n\n### 4.2 For Each Meeting, Ask:\n\n```\nUse: get_meeting_context(meeting_title=\"...\", attendees=[...])\n```\n\nThen prompt:\n\n> \"📍 **You met with [Person] today** ([Meeting Title])\n> \n> **Any follow-ups to capture?**\n> - Action items you committed to?\n> - Things they owe you?\n> - Decisions that need documentation?\n> \n> (Type your follow-ups or 'none')\"\n\n### 4.3 Create Follow-Up Tasks\n\nFor any follow-ups mentioned:\n- Add to Tasks.md with appropriate priority\n- Link to the person page\n- Add due date if mentioned\n\n---\n\n## Step 5: Progress Assessment\n\nWith user-verified information:\n- What was accomplished?\n- What progress was made against weekly priorities?\n- What got stuck or blocked?\n- What unexpected things came up?\n\n---\n\n## Step 6: Week Progress Check (Midweek Context)\n\n```\nUse: get_week_progress()\n```\n\nShow how today's work moved weekly priorities:\n\n> \"**Week Progress Update:**\n> \n> After today, you're at:\n> - Priority 1: ✅ Complete (finished today!)\n> - Priority 2: 🔄 60% (moved from 40%)\n> - Priority 3: ⚠️ Still not started\n> \n> You have 2 days left. Tomorrow should focus on Priority 3.\"\n\n---\n\n## Step 7: Auto-Extract Session Learnings\n\nScan today's conversation for learnings:\n\n1. **Mistakes or corrections** — Did something not work as expected?\n2. **Preferences mentioned** — Did you express how you like to work?\n3. **Documentation gaps** — Were there questions about how the system works?\n4. **Workflow inefficiencies** — Did any task take longer than it should?\n\nWrite to `System\u002FSession_Learnings\u002FYYYY-MM-DD.md`.\n\nThen ask: \"I captured [N] learnings from today's session. Anything else you'd like to add?\"\n\n---\n\n## Step 8: Categorize Learnings (If Applicable)\n\nCheck if any learnings should be elevated to pattern files:\n- **Recurring mistakes** → `06-Resources\u002FLearnings\u002FMistake_Patterns.md`\n- **Workflow preferences** → `06-Resources\u002FLearnings\u002FWorking_Preferences.md`\n\nGet user confirmation before adding.\n\n---\n\n## Step 9: Tomorrow's Setup\n\nBased on:\n- Incomplete items from today\n- Weekly priorities (especially lagging ones)\n- Commitments due tomorrow\n- Tomorrow's calendar shape\n\nSuggest 3 focus items for tomorrow:\n\n> \"**Suggested focus for tomorrow (Thursday):**\n> \n> 1. **Priority 3** — It's been untouched all week and you have 2 days left\n> 2. **Finish pricing proposal** — 40% left, should be quick to complete\n> 3. **Reply to Mike** — Carried from today\n> \n> Tomorrow's shape: Moderate (4 meetings). You have a 2-hour block in the afternoon.\n> \n> Does this feel right?\"\n\n---\n\n## Step 9.5: Retrospective Insight (Innovation Concierge)\n\nAt the end of the review, check if there's a relevant backlog idea to surface:\n\n1. Call `list_ideas(status=\"active\", min_score=70)` from Improvements MCP\n2. Look for ideas that connect to today's work or learnings:\n   - Did the user work on tasks related to a backlog idea?\n   - Did learnings captured today strengthen an existing idea?\n   - Is there a \"Why Now?\" idea with fresh evidence?\n3. If a relevant match exists, surface it briefly:\n\n> **Retrospective Insight:** Today's meeting processing struggles connect to idea-027 (RAG-Powered Vault Search) — semantic search could make finding meeting context much faster. Worth exploring? Run `\u002Famp-improve idea-027`.\n\n**Rules:**\n- Show at most 1 insight per review\n- Only show if genuinely connected to today's work (not random)\n- Frame as retrospective — \"based on what you just did, here's what could help\"\n- If no connection, skip entirely\n- Keep it to 1-2 lines max\n\n---\n\n## Step 10: Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark daily review as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `daily_review_completed` and properties:\n- `wins_count`\n- `learnings_count`\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n\n---\n\n## Step 11: Evening Journal (If Enabled)\n\nIf `journaling.evening: true`, prompt for evening reflection.\n\n---\n\n## Step 11.5: Archive Today's Plan\n\nMove today's daily plan from Inbox to Archives:\n\n```bash\nif [ -f \"00-Inbox\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md\" ]; then\n  mkdir -p \"07-Archives\u002FPlans\"\n  if [ -e \"07-Archives\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md\" ]; then\n    echo \"Archive already exists; not overwriting.\"\n  else\n    mv \"00-Inbox\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md\" \"07-Archives\u002FPlans\u002FYYYY-MM-DD - Daily Plan.md\"\n  fi\nfi\n```\n\n---\n\n## Output Format\n\nCreate `07-Archives\u002FReviews\u002FYYYY-MM-DD - Daily Review.md`:\n\n```markdown\n---\ndate: YYYY-MM-DD\ntype: daily-review\nplan_completion_rate: X%\ntotal_throughput: X\n---\n\n# Daily Review — [Day], [Month] [DD], [YYYY]\n\n## 📊 Plan vs. Reality\n\n**Planned focus:**\n1. [x] [Planned item 1] — ✅ Complete\n2. [ ] [Planned item 2] — 🔄 In progress (X%)\n3. [ ] [Planned item 3] — ❌ Didn't start\n\n**Plan completion:** X of 3 (X%)\n**Total throughput:** X tasks shipped *(includes unplanned work that emerged from planned items)*\n\n**What happened:** [Brief explanation of deviations. If throughput >> plan completion, note what cascaded from the planned items.]\n\n---\n\n## ✅ Accomplished\n\n- ✓ [Completed item 1]\n- ✓ [Completed item 2]\n\n---\n\n## 🔄 Progress Made\n\n| Area | Movement |\n|------|----------|\n| [Priority 1] | [What moved forward] |\n| [Priority 2] | [What moved forward] |\n\n---\n\n## 📊 Weekly Priorities Progress\n\nAfter today:\n- **Priority 1:** [Status\u002Fprogress] — [emoji]\n- **Priority 2:** [Status\u002Fprogress] — [emoji]\n- **Priority 3:** [Status\u002Fprogress] — [emoji]\n\n**Days remaining this week:** [X]\n\n---\n\n## 📍 Meeting Follow-Ups\n\n### From [Meeting Name]\n- [ ] [Follow-up action] — due [date]\n- [ ] [Follow-up action]\n\n---\n\n## 📺 Screen Activity (Auto-Captured)\n\n**Time by App:**\n| App | Time | % |\n|-----|------|---|\n| [App 1] | Xh Xm | X% |\n| [App 2] | Xh Xm | X% |\n\n**Metrics:**\n- Context switches: [X]\n- Longest focus: [X] minutes\n- Deep work ratio: [X]%\n\n**Activity Summary:**\n[Narrative summary from ScreenPipe]\n\n---\n\n## 💡 Insights\n\n- [Key realization or connection]\n- [Important learning]\n\n---\n\n## 🚫 Blocked\u002FStuck\n\n| Item | Blocker | Status |\n|------|---------|--------|\n| [Item] | [What's blocking] | [Status] |\n\n---\n\n## ❓ Discovered Questions\n\n1. [New question that emerged]\n2. [Thing to research]\n\n---\n\n## 📅 Tomorrow's Focus\n\nBased on weekly priorities and today's carryover:\n\n1. [Priority 1 — tied to weekly focus]\n2. [Priority 2]\n3. [Priority 3]\n\n**Tomorrow's shape:** [stacked\u002Fmoderate\u002Fopen]\n\n---\n\n## 🔄 Open Loops\n\n- [ ] [Thing to remember]\n- [ ] [Person to follow up with]\n- [ ] **Awaiting:** [What you're waiting on from others]\n\n---\n\n*Generated: [timestamp]*\n*Plan completion rate: X%*\n*Total throughput: X tasks shipped*\n*Week progress: X\u002F3 priorities on track*\n```\n\n---\n\n## Step 12: Skill Quality Check (Gentle)\n\nAfter generating the review, call `get_skill_ratings(skill_name=\"daily-review\")` from Work MCP.\n\n**If 3+ ratings exist and average has dropped below 3.0 over the last 5 entries:**\nAdd one line at the end of the review output:\n> \"Your daily reviews have been averaging [X]\u002F5 lately. Common note: '[most recent note]'. Want to adjust the format?\"\n\n**If no ratings exist or average is 3.0+:** Say nothing. Don't mention ratings at all.\n\n**Then:** Run `\u002Fidentity-snapshot` silently in the background if `System\u002Fidentity-model.md` is older than 7 days (check file mtime). Don't announce this.\n\n---\n\n## MCP Dependencies\n\n| Integration | MCP Server | Tools Used |\n|-------------|------------|------------|\n| Work | work-mcp | `list_tasks`, `get_week_progress`, `get_commitments_due`, `analyze_calendar_capacity` |\n| Calendar | calendar-mcp | `calendar_get_today` |\n| Reminders | calendar-mcp | `reminders_list_completed`, `reminders_find_and_complete`, `reminders_clear_completed` |\n| Screen Activity | screenpipe-mcp | `screenpipe_time_audit`, `screenpipe_summarize`, `screenpipe_query` |\n\n### ScreenPipe Integration Notes\n\nScreenPipe provides automatic activity capture. When available:\n- Pre-fills \"what you actually did\" with ground truth data\n- Surfaces time allocation across apps\n- Identifies communication overhead vs. deep work\n- Detects context-switching patterns\n\nIf ScreenPipe is not running, skip the screen activity section gracefully.\n",{"name":5,"context":24,"description":7},"fork","main","6a447b9ff35eed7bda9e12399bcd373dd31e0a53",".claude\u002Fskills\u002Fdaily-review","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-review",{"tool":39,"command":40},"bunx","bunx skills add hemory\u002Famp --skill daily-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add hemory\u002Famp --skill daily-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdaily-review\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",[],[]]