---
name: life-os-day-review
description: >-
  Review Aren's completed and unfinished day, capture wins and decisions, resolve or carry open commitments, and prepare tomorrow from TickTick, communications, Obsidian, and available health context. Use for "review my day", "prepare tomorrow", "evening review", or the scheduled evening run. Do not use for creating the morning plan before the day begins.
---

# Life OS Day Review

Compare intended work with evidence of what actually happened, then make tomorrow easier. Do not equate an unchecked task with failure or infer completion from silence.

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

## Step 1 — reconstruct today

Read:

- today's TickTick completed, open, overdue, and calendar items;
- commitments created, resolved, or still open;
- sent and unresolved Gmail/iMessage threads without reproducing bodies;
- today's Obsidian journal, meeting, and decision notes;
- available activity/focus or health trends as context only.

Run `lifeos health-scan` before reading Apple Health context. Synchronize Oura only for the bounded period needed by the review when it is authorized.

Separate observed facts from inferred outcomes. Ask Aren a maximum of three questions, and only for matters the data cannot answer: what is worth remembering, what still occupies attention, and what should move/delegate/cancel.

## Step 2 — close loops carefully

Resolve a derived commitment automatically only when a reply, completed task, or other unambiguous evidence closes it. Otherwise propose resolution. Do not complete or delete an authoritative source item merely because the review thinks it is stale.

## Step 3 — prepare tomorrow

Read tomorrow's schedule, deadlines, and preparation needs. Propose three priorities and identify unrealistic load. Any calendar move or material due-date/priority change requires confirmation.

## Step 4 — write the durable review

Create one date-keyed Obsidian note in the configured review root. Include wins, decisions, unfinished work, open communication, what is worth remembering, and tomorrow's priorities. Record the completed review with `lifeos review-record`.

Do not paste email or message contents. Use relationship/project labels and source references.

## Step 5 — deliver

Return a compact digest: what moved, what remains open, the one decision that matters, and tomorrow's three priorities. If the run lacks a required source, name the blind spot.