task-breakdown

# Task Breakdown Turns a session's **per-request breakdown** (the deterministic `request_units` emitted by session-metrics) into **semantic tasks** the user actually thinks in — "added auth", "debugged the cache miss" — and labels each with a verdict. You do the one thing deterministic code can't: decide which requests belong to the same task. The script does everything else (cost, turns, tokens, waste signals, the themed page). **Model.** This skill runs on your session's current model. It no longer pins one (a hard `model:` pin ran the inline turn on that model, dragging the whole conversation into that model's context window — on a long session that overflowed and broke invocation). The grouping + verdict work is judgement-heavy, so it wants a capable model; for a cheaper run that's still strong enough, `/model sonnet` before invoking. Don't drop to Haiku — the semantic verdicts need the headroom. **Division of labour — do not blur it:** - **The export owns the numbers.** Every cost / turn / token / waste figure comes from `request_units` in the JSON export. You MUST NOT sum money or invent figures — `--render-tasks` recomputes all totals from the export. - **You own the grouping + labels only.** You assign each `request_unit_id` to a task, write a short title, a verdict, and a one-line rationale. ## Inputs `$ARGUMENTS[0]` (optional) = path to a session-metrics JSON export, e.g. `exports/session-metrics/session_<id8>_<ts>.json` (session scope is the primary targ...