← ClaudeAtlas

gaia-issue-resolverlisted

End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue properly", or /gaia-issue-resolver. Works any gaia-research org repo — gaia-skill-tree, gaia-research, gaia-skill-heaven — while the issue itself lives on the headquarters tracker, gaia-research/gaia-skill-tree. Assumes the issue is already triaged and carries a P0–P4 label; if it does not, run /gaia-triage first.
gaia-research/gaia-skill-heaven · ★ 4 · AI & Automation · score 60
Install: claude install-skill gaia-research/gaia-skill-heaven
# gaia-issue-resolver Execute the complete resolution pipeline on **one** already-triaged Gaia issue, selected by priority (`P0`–`P4`) or assignee. Adapted from `favorchurch/rock-steward`'s `rock-issue-resolver`; the six-phase shape and the Kill Criteria discipline are its contribution, the Gaia mechanics below are this repo's. Prerequisite: the issue is triaged — it has a priority label, a size, and a stated problem. If it doesn't, stop and run `/gaia-triage` on it first. This skill resolves; it does not decide what is worth resolving. --- ## 1. Non-negotiables 1. **Zero follow-up debt.** Do not close an issue by filing a trailing "clean up" issue that carries its own unfinished work. Everything a reasonable reviewer would call a direct consequence of this change belongs in this change. This is `gaia-skill-tree`'s sprint-completeness rule applied at issue granularity: genuinely new, out-of-scope work discovered along the way may still be filed; the issue's own remainder may not. 2. **Kill Criteria before code.** Every acceptance requirement is written as an explicit `KC-1 … KC-N` list, posted as a comment on the issue *before* implementation starts, and checked off from evidence before closing. An issue with no Kill Criteria has no definition of done. 3. **Draft PR first, push often.** Branch, then open a **draft** PR as the first git operation after the first commit — before the work is finished. Push after each phase. Draft PRs stay draft un