deliver-issuelisted

Take ONE idea or ONE planned issue all the way to a merged PR, hands-off — file or seed it with create-issue, build it with implement-issue, land it with merge-pr, each phase in a FRESH sub-agent context. Use when the user wants the whole chain run for a single item: "deliver issue 47 end to end", "take this idea to a merged PR", "run the full lifecycle on #12", « livre l'issue 47 de bout en bout », « de l'idée à la PR mergée ». `--stop-at ready` stops before the merge. Does NOT apply to many issues at once (auto-dev), to landing a PR that is already open (merge-pr), to only filing an issue (create-issue), or to building one you will merge yourself (implement-issue).
phmatray/ai-migration-kit · ★ 3 · AI & Automation · score 75

Install: claude install-skill phmatray/ai-migration-kit

# Deliver an issue — one item, idea to merged PR, hands-off ## What this does The lifecycle is three skills the user types one after another — `create-issue` ends with `/implement-issue #N`, `implement-issue` ends with `/merge-pr #PR`, `merge-pr` lands it — and [`../_shared/recap.md`](../_shared/recap.md)'s hand-off table exists because those prompts are what the user acts on next. `auto-dev` walks that chain for N issues at once through two fresh-context worker commands. This skill is the **single-item form**: one idea or one planned issue, taken to a merged PR, with the same two command files doing the work and this skill doing only the deciding. It is an **orchestrator, never an implementer**. It runs nothing of the three phases in its own context: each phase is a fresh sub-agent dispatched through the Agent tool (ADR 0007), its final message is read as a report, and the decision between phases is made here. The reason is measured, not stylistic — `commands/auto-dev-worker.md` § *Why two phases* records the merge phase at ~247K tokens of context per turn when run inside the implement context, and ~82% cheaper in a fresh one. Inlining the three bodies here would reintroduce the cost `auto-dev` split away. **Nothing new executes.** The phase prompts are [`../../commands/auto-dev-worker.md`](../../commands/auto-dev-worker.md) (phase 1: `implement-issue` up to a ready PR, with the never-wait rule, the turn budget and the untrusted-input boundary it already carries) and [`.