---
name: plan-day
description: Review the authenticated Uredan planner and build a focused plan for a saved-local day, with optional confirmed moves and ordering. Use when a user asks to plan today, plan a specific day, choose priorities, or turn Braindump and backlog work into a day plan.
---

# Plan Day

Build the plan from current server state and the user's saved timezone. Keep the
recommendation distinct from mutations to the planner.

## Workflow

1. Read `preferences_get` to determine the saved timezone and resolve the
   requested day. State the explicit local date when “today” could be unclear.
2. Read the requested day plus relevant Braindump, Weekly Backlog, overdue, and
   already planned work with `tasks_list_v2` or `tasks_query`. Follow bounded
   cursors when the result says more matching work exists.
3. Preserve current completion, List organization, placement, due dates,
   priorities, estimates, and ordering in the summary. Never treat a due date
   as planner placement or vice versa.
4. Ask only for constraints that materially affect the plan, such as available
   time or a hard priority. Otherwise make a concise recommendation from the
   confirmed tasks and clearly label assumptions.
5. Show the proposed day order and any moves. Wait for confirmation before
   applying this broad plan, unless the user already specified each exact move
   and order.
6. Apply approved placement changes with `tasks_move_v2` and ordering with
   `tasks_reorder_v2`, using the current server versions and semantic anchors.
   Re-read and ask before changing the proposal after a conflict.
7. Summarize server-confirmed changes and call out anything left unchanged.

## Guardrails

- Never create, complete, trash, permanently delete, change due dates, or
  change List organization as an implicit part of planning.
- Prefer a smaller realistic day over silently moving every unfinished item.
- Never request or pass an owner ID, token, OAuth code, raw position, or sort
  key.
- In read-only mode, provide the plan as a recommendation and report that the
  server rejected mutations. Do not claim the planner changed.
- If no matching tasks exist, say so and offer capture; do not manufacture work.
- If authentication is unavailable, direct the user to the host's Uredan OAuth
  connection without asking for credentials in chat.