/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`."

Execution mode

Run inline in the current conversation by default, so this work can see what the user has already discussed, decided, or settled this session. Do not fork merely because this skill was selected. Only run in the background when the user explicitly asks for a background run or the host has already obtained a specific background-work approval for this run.

Delegated gathering (large-vault scaling)

This skill stays inline as described above: it keeps session awareness, it asks the user the questions, and it owns every interactive step. What it does NOT do inline is the bulk read-gathering, which on a mature vault (hundreds of notes, thousands of indexed messages, a live calendar and multiple integrations) can be large enough to exhaust the main conversation before the useful work starts.

So the gathering phase is delegated to one `general-purpose` subagent via the Agent tool, using the self-contained prompt in this skill's `AGENT_INSTRUCTIONS.md`:

1. Read `.claude/skills/week-review/AGENT_INSTRUCTIONS.md`. 2. Substitute its placeholders (`{{TARGET_DATE}}`, `{{WEEK_START_DATE}}`, `{{TARGET_DATE_PLUS_1}}`, `{{DAY_NAME}}`, `{{MONTH}}`, `{{DD}}`, `{{YYYY}}`). 3. Call the Agent tool with `subagent_type: "general-purpose"`, that prompt, and a short description. 4. Verify it wrote the synthesis to `00-Inbox/Weekly_Synthesis_YYYY-MM-DD.md`, then run the interactive review from its structured findings.

The subagent inherits MCP connections, runs in its own context, and that context is freed when it completes, so only its findings reach this conversation.

**Use `AGENT_INSTRUCTIONS.md` verbatim.** Read the file and pass its content as the subagent prompt, substituting only the placeholders. Do NOT hand-write a replacement brief from what you already know about the week: that is how steps get silently dropped, and the omission looks complete because nothing errors. If context from this conversation is worth adding, APPEND it to the file's content; never substitute for it.

**Two caveats that are load-bearing:**

• **Do not count on hooks for the subagent's writes.** The hooks declared in

this skill's own frontmatter belong to this skill's run, not the subagent's, and whether the repository-wide hooks in `.claude/settings.json` reach a subagent's tool calls is not something a skill should assume either way. Nothing in this skill's gathering depends on a hook; the subagent's writes must stand on their own.

• **Always fall back.** If the subagent fails, times out, or returns nothing

usable, say so plainly and run the gathering inline from the same `AGENT_INSTRUCTIONS.md`. A missing subagent must never mean a missing result.

**Stays inline:** the whole interactive review, priority-by-priority assessment, pattern discussion, goal updates, career evidence capture, next week's priority confirmation, the Dex Inbox check (Step 0.5), clearing completed tasks from `03-Tasks/Tasks.md` after confirm (the delegated summary names this step), and the `/identity-snapshot` run that follows the synthesis. The subagent gathers evidence; it does not make judgements.

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. Exception: if the tool says Reminders can't be switched on from inside VS Code, tell the user that one calm line (use the Claude app or Terminal for Reminders). Do not skip that case silently, do not advise reinstalling, and do not raise it again this session.

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

• Resolved daily-plan folder (`System/folder-paths.yaml` `daily_plans`, else the folder that already holds dated daily plans, else `00-Inbox/Daily_Plans/YYYY-MM-DD.md`) — This week's daily plans (primary record of pl