---
name: life-os-weekly-review
description: >-
  Reconstruct Aren's week from TickTick, commitments, Gmail/iMessage follow-ups, Obsidian notes and goals, decisions, relationships, and available health trends; challenge stale work and write the canonical weekly review to Obsidian. Use for "weekly review", "review my week", "plan next week", or the scheduled Sunday review. Do not use for a single-day recap.
---

# Life OS Weekly Review

Explain what actually changed, which loops remain open, and what deserves next week's limited attention. The canonical artifact is Obsidian; the Codex task receives a concise delivery summary.

Read `../../runtime/references/workflow-contract.md` and use `../../runtime/templates/weekly-review.md`.

## Step 1 — set the exact period

Use the configured timezone and explicit start/end dates. Check whether a review already exists for that period before writing.

## Step 2 — reconstruct evidence

Gather:

- TickTick completed, overdue, upcoming, calendar/time blocks, habits, and focus records;
- commitments opened, resolved, waiting, and repeatedly carried;
- Gmail/iMessage open loops and important relationship activity, summarized without bodies;
- Obsidian journal, meeting, decision, goal, and active plan changes;
- Oura and Apple Health trend-level context when fresh;
- last week's stated priorities for planned-versus-actual comparison.

Run `lifeos health-scan` before reading Apple Health context. When Oura is authorized, synchronize exactly the review period before analyzing trends.

Label missing sources and freshness. Do not infer a quiet week from an inaccessible connector.

## Step 3 — analyze honestly

Cover wins, decisions, lessons, promises to/from others, unresolved communication, active/stalled/neglected projects, relationships needing attention, health/energy patterns, and next week's events/deadlines.

Challenge work that repeatedly survives reviews: delete it, delegate it, schedule it, clarify it, or consciously recommit. Never delete or materially reschedule it without confirmation.

## Step 4 — write once

Create one canonical review note in the configured Obsidian review root. Preserve source references and avoid raw private messages. Record the review period and note reference with `lifeos review-record`; this is the idempotency gate.

## Step 5 — deliver decisions

Return:

1. the week's short narrative;
2. the three most important wins;
3. open loops requiring Aren;
4. one stale thing to decide;
5. next week's three priorities and preparation risks;
6. the Obsidian note path.