backloglisted

Interactive dispatcher for backlog work. Asks one routing question — drive PRs to merge, or implement issues to open-PR state — then follow-ups based on the answer, and hands off to implement-issues / babysit-pr with standing policy applied. Use when asked to work the backlog or run /backlog.
lgtm-hq/ai-skills · ★ 0 · AI & Automation · score 69

Install: claude install-skill lgtm-hq/ai-skills

# Backlog Route a backlog session to the right workflow via a short interview, then dispatch to `implement-issues` and/or `babysit-pr`. This skill decides and delegates — it implements nothing itself. ## Invocation - `/backlog` — run the interview below. - Args answer questions in advance; skip any question already answered: - `/backlog merge` / `/backlog open-pr` - `/backlog merge #124 #125` — explicit PR list - `/backlog open-pr #12 #14` — explicit issue list ## Interview Ask with structured multiple-choice questions (AskUserQuestion in Claude Code; plain questions elsewhere). One round per step — this is a router, not a grilling. ### Q1 — Goal > What should this session drive toward? - **merge-pr** — take PRs (and optionally fresh issues) all the way to merged, releases included. - **open-pr** — implement issues and stop at merge-ready open PRs; the human merges. ### Q2 — branch on the answer **If merge-pr:** > What's in scope? - **All open PRs** in the repo (default). - **Specific PRs** — take the list from args or ask. - **Issues first, then all PRs** — run `implement-issues` on issues without PRs, then babysit everything open. **If open-pr:** > Which issues? - **All open issues without a PR** (default). - **Specific issues** — take the list from args or ask. Do not ask about repo (use the current checkout), sub-agents, lint, or release handling — those are fixed by standing policy below. ### Q3 — Plan confirmation (deliberate, keep it) The