tracklisted

# Tracking complex tasks The tools are `TaskCreate`, `TaskUpdate`, `TaskList`, `TaskGet`. ## The `--wss-track` shorthand `--wss-track` invokes this immediately, with no confirmation, and overrides the threshold below: build the list even for work you would otherwise have judged too small. It authorizes nothing else — this skill writes no file and touches no record, so there is nothing for a grant to confer. Where a flag counts is [`README.md`](../../README.md); what it authorizes is the block `wss-shorthand-flags.sh` injects and [`wss/workflow/WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md)'s matrix — the two copies `wss-doctor.sh` compares, never restated per skill. ## The threshold Build a list when **any** of these is true: - The work has **3 or more distinct steps** that can each be finished and verified on their own. - It touches **more than one file or subsystem**. - The user **listed several things** — numbered, comma-separated, or just "do X and also Y". - You cannot state the whole plan in **one sentence** without an "and then". - You are **mid-task and it grew**. Late is much better than never; build the list the moment you notice. Skip it — and just do the work — when it is a single edit, a question, a lookup, a one-file change, or a conversational turn. A one-item list is noise. ## Build the whole list before starting Create every task you can foresee **up front**, in one message with parallel `TaskCreate` calls, then start. A list that gro