gza-task-triagelisted

# Gza Task Triage Walk the `gza incomplete` "needs attention" list (or a single lineage) and decide, row by row, what the correct corrective action is. The output is a per-row classification plus a recommended `gza` command; this skill **asks before doing anything** — including drops. This skill exists because the same conversation keeps recurring: `gza watch` runs the easy cases and leaves a small pile of merge units in `gza incomplete` that each need a judgment call. The slot below `watch` is the human triage step, and this skill systematizes it. ## What this skill MUST NOT do These guardrails are load-bearing. Do not relax them. - **Do not merge** — never run `gza merge` or `git merge`. - **Do not retry or resume** — never invoke `gza retry` or `gza resume` on your own. If a row looks like it warrants a resume, say so and stop; let the user run it. - **Do not delete branches** — never `git branch -D` or otherwise mutate refs. - **Do not edit code** — for review/improve churn that needs a real code fix, hand off to `/gza-task-fix` rather than editing inline. - **Ask per row** — even for safe-looking drops, ask before executing. If you find yourself wanting to do any of the above without explicit per-row confirmation, stop and report instead. ## Process ### Step 1: Resolve scope The skill accepts an optional task ID. - **With ID:** triage just that lineage. Resolve the merge-unit owner via `gza show <id>` and look at the row that owns it. If the ID is not currently