devpilot-resolve-issueslisted

# Resolve GitHub Issues (Loop Until Done) ## Files in this skill | File | When to load | |---|---| | `references/worktree-management.md` | Step 0 (preflight prune) and Step 5 (per-issue create) and the cleanup path — path scheme, create / remove, failure modes. | | `references/verdict-comments.md` | Step 4 — exact comment bodies for the three verdicts. | | `references/task-decomposition.md` | Step 6a — split a REAL issue into 1–3 tasks. | | `references/subagent-spec.md` | Step 6b — the spec handed to each per-task implementer subagent. | | `references/per-task-review.md` | Step 6c — invoke `superpowers:requesting-code-review` after each task. | ## Overview End-to-end loop that takes open GitHub issues from triage to reviewed PR, one at a time, until the filter returns no matches. Each issue ends in exactly one of three states: **closed with reason** (false positive), **escalated with questions** (needs human), or **reviewed PR opened** (real). Nothing else is a valid terminal state. Every REAL issue is fixed in its **own `git worktree`**, not in the main checkout. The main checkout stays on the default branch, untouched, so the user can keep working in it while the loop runs. The fix branch and all its commits live in a sibling directory at `<repo-root>.worktrees/issue-<N>-<slug>/`. See `references/worktree-management.md` for the lifecycle. For a REAL issue, the fix itself follows the `superpowers:subagent-driven-development` pattern: decompose into a small number of ta