run-backlog

Run Backlog

Work off the project's planned backlog. Pick milestones (or loose issues), then refine → implement → test/QA → ship each selected item, one after another, until the backlog is done — so the user can lean back or go to bed and wake up to shipped work.

Architecture — standalone, compose-not-copy. This skill owns its own control flow and is itself the ship instance. It does NOT modify run-autonomous and never routes a ship through it — run-autonomous cannot ship by design, and a task string never overrides that guardrail. Instead this skill reuses the autonomous frame by calling the same plugin scripts (permission audit, shutdown timer, resume schedule, watchdog, completion card) and referencing the same deep-knowledge, and composes /concept, /ship, and the role agents as building blocks. Full rationale + reuse table (dated design spec, kept under its original name): docs/superpowers/specs/2026-07-18-devops-burn-backlog-design.md.

Step 0 — Load Extensions

Silently check (do not surface "not found"):

1. ~/.claude/skills/run-backlog/SKILL.md + reference.md
2. {project}/.claude/skills/run-backlog/SKILL.md + reference.md
3. Merge: project > global > plugin defaults

Step 0.1 — Auto-Start / Resume Re-entry

If the incoming message starts with RUN_BACKLOG_AUTOSTART:, a presence-phase timeout fired and the user is AFK. Step 1a arms this cron before the first question, and every presence question re-arms it, so the timeout covers the whole Präsenz phase — not just the final confirmation. Do NOT re-ask anything. Parse phase, queue, milestones, shutdown, autoResume, burnMode, branch.

Pending-question guard: if an AskUserQuestion is still active when the prompt arrives (the user is mid-answer), do NOT auto-start — re-arm a fresh one-shot cron at now + 3min with the same prompt and keep waiting (log "Autostart verschoben — offene Frage aktiv").

Otherwise branch on phase:

• phase=gate — the full gate completed (permissions primed, queue + shutdown/resume chosen). Output once "Timeout — starte Backlog-Runner autonom.", skip Steps 1–3, jump to the Step 4 loop.
• phase=presence — the user left before finishing the gate. Timeout defaults apply and are not renegotiable:
  • shutdown=yes always. It is the only sensible default for a walked-away user (a report-only run nobody returns to just idles the PC all night).
  • burnMode=no always. The presence default is the normal sequential run; budget mode is a deliberate opt-in, never auto-enabled on a timeout.
  • queue = the default encoded at arm time: every open milestone's issues (or every open loose issue when there are no milestones). Use a partial selection if one was already made before the timeout.
  • Skip Step 2 entirely. Concept decisions need the user and refine writes to GitHub (presence-only). Park every needs-decision / oversized item as a ⏸ Rückfrage for the report; run only the ready / plain issues.
  • Run Step 3 non-interactively: permission audit + artifact hygiene, then arm the lockout and the watchdog with shutdown=yes. Skip the permission-audit question — proceed with already-granted permissions; anything not in settings.json cannot be primed AFK and falls to the per-issue late-permission protocol (deep-knowledge/autonomous-execution.md). Output once "Timeout in Präsenz-Phase — starte mit Defaults (alle offenen Milestones, Shutdown).", then jump to the Step 4 loop.