---
name: capture-work
description: Capture one or more tasks in the authenticated Uredan planner, including optional notes, priority, estimate, List, planner placement, and due date. Use when a user asks to add, capture, record, or organize work in Uredan.
---

# Capture Work

Capture only the work the user supplied. Preserve Uredan's independent
organization, planner placement, and due-date concepts instead of inferring
that they are interchangeable.

## Workflow

1. Extract each title and any explicit notes, planned minutes, priority, List,
   planner day or Weekly Backlog, and due date.
2. If the user uses a relative date, read `preferences_get` and resolve it in
   the saved IANA timezone. Send explicit `YYYY-MM-DD` dates to tools.
3. Use `lists_list` when a named List must be resolved. Ask a short question if
   more than one interpretation remains; never guess a task, List, date, or
   placement identity.
4. Treat a direct request such as “add X to Braindump” as approval for that
   exact recoverable write. For inferred organization or a multi-step
   reorganization, show the proposed changes and wait for confirmation.
5. Create each task with `tasks_create_v2`. Prefer setting known organization,
   placement, priority, estimate, and due date in that single call rather than
   following with avoidable mutations.
6. Report only server-confirmed results. If a task conflicts or a write is
   rejected, describe that item as unchanged and offer a bounded retry.

## Guardrails

- Never request or pass an owner ID, access token, OAuth code, client secret,
  raw position, or sort key.
- Do not invent missing task details. Default only unspecified organization and
  placement to the server's normal Braindump behavior.
- Do not mark tasks complete, move existing tasks, or delete anything unless
  the user explicitly asks.
- If Uredan is read-only, preserve the capture list in the response and explain
  that the server rejected writes; do not claim success or seek a bypass.
- If authentication is unavailable, ask the user to connect Uredan through the
  host's OAuth flow. Never ask them to paste credentials into chat.