/daily-review

name: daily-review
description: "Close out the day: what got done vs planned, meeting follow-ups, learnings, and tomorrow's focus. Use when the user says 'review my day', 'wrap up', 'end of day', or it's evening. Also use proactively when the day's work is clearly done. Not for setting up the morning; use `daily-plan`."

Purpose

Conduct an end-of-day review to capture progress, track what you actually accomplished vs. planned, surface meeting follow-ups, and set up tomorrow.

Execution mode

Run inline in the current conversation by default. Do not fork merely because this skill was selected. Only run in the background when the user explicitly asks for a background review or the host has already obtained a specific background-work approval for this review.

Before authoring anything, check for existing day state: today's archived plan, today's completion metrics, and any review or closeout already written for today. If existing day state is present, enter **verifier mode**. Read it, compare it with the current tasks and meeting evidence, and surface omissions or proposed corrections. Do not create a competing review or overwrite the existing author. Any proposed write still follows the confirmation and write-guard rules below.

Tone Calibration

Read `System/user-profile.yaml` → `communication` section and adapt accordingly.

---

Step 1: File Discovery

Find files modified TODAY:

TODAY=$(date +%Y-%m-%d)
find . -type f -name "*.md" -newermt "$TODAY 00:00:00" ! -newermt "$TODAY 23:59:59" 2>/dev/null

**Critical rules:** 1. No truncation — list all modified files 2. Today only — use date-based filtering 3. Verify with user — "These are the files I found. What did you actually work on?"

---

Step 1.5: Process Today's Meetings

Before gathering context, ensure today's meetings are in the vault by running `/process-meetings today`. This pulls any unprocessed meetings from the meeting source (Otter.ai, Granola, etc.), creates meeting notes, updates person/company pages, and extracts tasks — so the rest of the review has complete data.

• If no new meetings are found, continue silently
• If meetings are processed, note the count for the review summary
• Do NOT ask for a skill rating after this sub-step — save that for the end of the full review

---

Step 2: Gather Context

From 03-Tasks/Tasks.md

• Tasks completed today (look for `✅ YYYY-MM-DD` matching today)
• Tasks started but not finished

From Weekly Priorities

Read `02-Week_Priorities/Week_Priorities.md` for:

• This week's strategic focus
• How today's work connects to weekly priorities

From Recent Meetings

Check `00-Inbox/Meetings/` for meeting notes from today (should now include anything just pulled from the meeting source).

---

Step 2.5: Semantic Context Enrichment (if QMD available)

**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.

What to search:

1. **Map completed tasks to goals:** For each task completed today, search semantically:

   qmd query "task description here" --limit 3

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.

2. **Enrich meeting follow-ups:** For each meeting today, search for related past discussions:

   qmd query "meeting topic" --limit 5

Surface any commitments, decisions, or context from previous meetings on the same theme.

3. **Priority alignment check:** For each weekly priority, search for today's work that advanced it:

   qmd query "priority title/description" --limit 5

Catch work that moved the needle but wasn't explicitly tagged to the priority.

How to use results:

• **Only surface genuinely new connections** — if a task was already linked to a goal, don't repeat it
• Merge insights into the Plan vs. Reality section: "Task X also advanced Goal Y (semantic match)"
• Add to the Weekly Priorities Progress section if semantic search reveals hidden progress
• If QMD is not available, skip this step silently — the review works fine without it

---

Step 2.55: Dex Inbox Check (Phone Captures)

Check for tasks added from phone during the day that weren't triaged in the morning plan:

Use: reminders_list_items(list_name="Dex Inbox")

**If the tool is unavailable or errors** (Apple Reminders phone-capture is optional and may not be set up on this machine): skip this step silently — do not surface an error for a feature the user never enabled. Note: Reminders access never works when Claude Code runs inside the VS Code extension (macOS never shows the permission dialog to that process) — see the known limitation in `06-Resources/Dex_System/Calendar_Setup.md`. Do not advise reinstalling or reconfiguring; skip silently.

If items found:

• Surface them: "📱 **Phone captures not yet triaged** (X items in Dex Inbox)"
• Run the same triage flow as daily-plan Step 5.10a: infer pillar, confirm with user, create task, mark Reminder complete
• If user wants to defer: leave in Dex Inbox for tomorrow's daily-plan

**If empty:** Skip silently.

**Setup:** If the user hasn't created a "Dex Inbox" Reminders list yet, mention it: "You can capture tasks from your phone by adding them to a 'Dex Inbox' list in Apple Reminders. They'll show up here automatically."

---

Step 2.6: Reminders Completion Sync (Dex Today → Dex)

Check if tasks were completed on phone since the morning plan:

Use: reminders_list_completed(list_name="Dex Today")

**If the tool is unavailable or errors** (Apple Reminders sync is optional and may not be set up on this machine): skip this step silently — do not surface an error for a feature the user never enabled. Note: Reminders access never works when Claude Code runs inside