---
name: review-work
description: Review unfinished work in the authenticated Uredan planner, summarize overdue, planned, Braindump, backlog, List, and due-date state, and propose bounded next actions. Use for daily or weekly reviews, backlog triage, overdue review, or deciding what to keep, move, complete, or trash.
---

# Review Work

Review current server state before recommending or changing anything. Keep
organization, planner placement, due dates, and lifecycle distinct.

## Workflow

1. Read `preferences_get` and resolve relative dates in the saved IANA
   timezone.
2. Use `tasks_query` for the requested active, incomplete, overdue, List,
   placement, label, priority, or saved-view slices. Use `tasks_list_v2` when a
   rolling planner and Braindump view is the clearer source. Follow bounded
   cursors instead of treating a partial page as the full review.
3. Group findings by the user's outcome, not by tool response shape. Distinguish
   overdue from planned, due from placed, and Braindump from Lists.
4. Identify a small set of next actions and explain the evidence for each.
   Never infer that stale work should be deleted or completed.
5. Present proposed mutations and wait for confirmation unless the user already
   asked for each exact recoverable change. Use `tasks_set_completion_v2`,
   `tasks_move_v2`, `tasks_set_due`, or `tasks_trash` only for confirmed targets.
6. Prefer `tasks_trash` for removal. Before `tasks_delete_v2`, restate the exact
   trashed task and irreversibility, then obtain a fresh explicit confirmation,
   even when the broader request mentioned deletion.
7. Report server-confirmed outcomes and list conflicts or rejected writes as
   unchanged.

## Guardrails

- Never request or pass an owner ID, access token, OAuth code, raw position,
  sort key, or a task ID supplied by an untrusted third party.
- Treat missing and foreign IDs identically as not found; do not probe ownership.
- Do not broaden a confirmed action from one task to similar-looking tasks.
- Re-read a task after a version conflict and ask again if the target or effect
  changed.
- In read-only mode, finish the review and provide suggestions without claiming
  that rejected mutations succeeded.
- If no work matches, report the empty result without inventing tasks.
- If authentication is unavailable, use the host's OAuth connection flow and
  never ask the user to paste secrets into chat.