/week-review

name: week-review
description: "Review the week with concrete accomplishments (not fake percentages), pattern detection and goal tracking. Use when the user says 'how was my week', 'week review', or it's their last working day. Also use proactively when a week's priorities are largely resolved. Not for planning the coming week; use `week-plan`."
context: fork

Purpose

Create a synthesis of the week reviewing activity, progress, and what was accomplished. **Uses concrete metrics, not vague percentages.**

Read `working_week.days` in `System/user-profile.yaml` and treat its last working day as the natural review point.

---

Step 0: Process Unprocessed Meetings

Before gathering data, ensure all meetings from this week are in the vault by running `/process-meetings`. 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 weekly synthesis has complete data.

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

---

Step 0.5: Dex Inbox Check (Phone Captures)

After processing meetings, check for tasks captured from phone that haven't been triaged:

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.

If items found:

• Surface them: "📱 **Phone captures not yet triaged** (X items in Dex Inbox)"
• Run triage flow: infer pillar, confirm with user, create task, mark Reminder complete
• If user wants to defer: leave in Dex Inbox

**If empty:** Skip silently.

---

Data Sources

1. Task Progress

• `03-Tasks/Tasks.md` — Task completion status
• `02-Week_Priorities/Week_Priorities.md` — Weekly priorities

2. Project Activity

• `04-Projects/**/*.md` — Modified this week

3. Meetings & People

• `00-Inbox/Meetings/*.md` — Meeting notes from this week
• `People/**/*.md` — Person pages updated

4. Learnings

• `06-Resources/Learnings/**/*.md` — Explicit learnings
• `System/Session_Learnings/*.md` — Auto-captured session learnings

5. Daily Plans & Reviews

• `07-Archives/Plans/YYYY-MM-DD.md` — This week's daily plans (primary record of planning ritual)
• `07-Archives/Reviews/Daily_Review_YYYY-MM-DD.md` — This week's reviews

6. Journals (If Enabled)

• `00-Inbox/Journals/YYYY/MM-Month/` — Morning/evening journals

---

Analysis Process

1. Weekly Priority Completion (Concrete, Not Percentages)

**Don't say:** "Goal X went from 40% to 55%" **Do say:** "You completed 2 of 3 weekly priorities"

Use: get_week_progress()

For each weekly priority:

• **Complete:** ✅ What was the deliverable? When did you finish?
• **In Progress:** 🔄 What specifically got done? What's left?
• **Not Started:** ❌ Why? Should it carry forward?

**Surface concrete accomplishments:**

> "**This week's priorities:** > > 1. ✅ **Ship pricing page** — Complete (pushed to prod Wednesday) > - Deliverable: New pricing page live at /pricing > - Tasks completed: 5 of 5 > > 2. 🔄 **Write Q1 strategy doc** — 60% complete > - Done: Outline, competitive analysis, recommendations > - Remaining: Executive summary, financial projections > - 2 tasks left > > 3. ❌ **Customer interviews** — Not started > - Reason: Calendar was too stacked > - Recommendation: Carry to next week with protected time"

1.5 Semantic Goal-to-Work Mapping (if QMD available)

**Check if semantic search is available** by looking for `qmd` in PATH.

If available, enhance the weekly priority review with meaning-based analysis:

1. **Auto-detect goal contributions:** For each completed task this week, search:

   qmd query "task title/description" --limit 3

against quarterly goals. Catch tasks that advanced goals without explicit links.

• Example: "Built customer health dashboard" semantically matches goal "Improve NPS tracking" — different words, same work.

2. **Cross-priority connections:** Search for work that bridges multiple priorities:

   qmd query "priority 1 description" --limit 5

Surface tasks that contributed to more than one priority.

3. **Thematic patterns:** Search for recurring themes across the week's work:

   qmd query "common theme from meetings/tasks" --limit 5

Detect patterns like "most of your work this week clustered around customer retention" even when tasks used different terminology.

**Integration:** Merge findings into the Quarterly Goals table — add a "Hidden contributions" row for semantically-detected but not explicitly-linked work. Only show genuinely new connections, not things already captured by keyword matching.

**If QMD unavailable:** Skip silently. Task completion stats still work fine.

2. Task Completion Stats (Concrete Numbers)

Scan `03-Tasks/Tasks.md` for completion timestamps from this week:

• Count tasks completed (look for `✅ YYYY-MM-DD` in date range)
• Count tasks added mid-week
• Count tasks carried over

**Surface:**

> "**Tasks this week:** > - Completed: 14 tasks > - Added mid-week: 6 tasks (scope creep?) > - Carried over: 3 tasks > > **Completion rate:** 82% (14 of 17 planned)"

3. Quarterly Goals Progress (Concrete Milestones)

**Don't use fake percentages.** Use milestone counts and specific accomplishments.

Use: get_quarterly_goals()
Use: get_goal_status(goal_id) for each goal

For each goal:

• Milestones completed this week
• Total milestones done vs. total
• Weeks since last milestone
• Specific accomplishments that moved the goal

> "**Quarterly Goals Progress:** > > | Goal | Milestones | This Week | Status | > |------|------------|-----------|--------| > | Launch v2.0 | 3 of 5 | +1 (Prici