taskslisted

# Tasks Use the `patcher tasks` CLI to understand the assigned task, keep its record useful, and report the outcome where the work is tracked. Delegation presets are user-defined; Tasks ships with none. Before dispatching work, use `patcher tasks preset list` and create a preset if the required one does not already exist. Dispatch requires an existing preset. ## Work a task 1. Find and read the task before acting: ```sh patcher tasks show ABC-12 ``` The detail includes the description, status, priority, labels, subtasks, comments, attachments, attached worker threads, and the GitHub pull requests those threads produced (from environment metadata, with state open/draft/merged/closed). Use `patcher tasks show ABC-12 --json` when the result will drive commands or code. For project-wide discovery, `patcher tasks list` returns at most 100 rows by default. Pass `--limit 1-500`; in JSON, continue with `nextCursor` via the same filters/sort and `--cursor <value>`. A task-list mutation makes an old cursor stale, so restart without it. 2. Fetch every relevant attachment before making assumptions about it: ```sh patcher tasks attachment get <attachment-id> --out <path> ``` 3. Do the work. Post one substantive comment at each meaningful milestone, such as a completed investigation, an implementation ready for validation, or a concrete blocker: ```sh patcher tasks comment ABC-12 --body "Implemented the change; focused val