jira-deliverylisted

# Purpose Turn a `needs-fix` verdict into real, verified, published work without the orchestrator (`@jira-task-runner`) ever editing code itself. This skill owns exactly six things: the isolated branch, the red-test-first step on change tickets, delegation to the right executor, the verification gate, the commit + PR, and the writeback. Anything that outgrows `jira.budget` mid-flight is not this skill's problem to solve — it hands off to `jira-escalation` (see [Related](#related)) and stops. # When to use Called by `@jira-task-runner`'s Fork (step 5), `needs-fix` row, strictly after `jira-triage` has produced the evidence bundle for **either** class: - **`class: defect`** — reproduction command, exit code, output fragment, extracted repro steps, for a ticket whose reproduction ran **red**. - **`class: change`** — the green baseline run, the absence proof (what was searched and what was found), and the numbered **testable acceptance criteria**. There is no red command yet: producing one is this skill's Step 2a, and it is a precondition for any implementation work. Never invoked directly on a `too-large` verdict — that never reaches this skill at all. # The class decides the shape of the run | | `class: defect` | `class: change` | |---|---|---| | Red evidence | Already in hand (`jira-triage`'s failing reproduction) | **Produced here, in Step 2a**, as a failing acceptance test | | Branch | `fix/<KEY>-<slug>` | `feat/<KEY>-<slug>` | | Worktree dir | `<worktree-root