← ClaudeAtlas

fix-looplisted

Run retries, stalls and the third attempt on a task. Use when a reviewer or QA FAIL or a judge reject comes back, when respawning a coder, when a task reaches attempt 2 or attempt 3, when a worker is lost, stopped or stalled, or when the findings are only nits.
volekerb/hivemill · ★ 33 · AI & Automation · score 75
Install: claude install-skill volekerb/hivemill
# Fix loop Rules for the build loop's failure paths. Follow these steps in order. 1. Triage the cause first (L1, L4). Run `factory task show T` and read the latest verdicts. - Worker lost or stopped, worktree clean, no commits beyond the base: it produced nothing (L1). Respawn it for the same task: `factory spawn <role> --task T`. This is not an attempt. - Partial or unpushed work is NOT no-work. Describe it in the next coder's `--prompt`, or ask that coder to push it first. - Only nit findings: do not respawn a coder (L4). Respawn the same verifier, not a coder (L6): `factory spawn reviewer|qa --task T --prompt -`, with a note to re-verdict under the severity rule. This is not an attempt. Its pane is closed after `factory done`, so nothing re-verdicts unless you spawn it. Park the nits: `--follow-up-of T` is refused until T is done (merged), so before the merge file a plain `factory task add` in the same goal and cite T in the title and spec; after the merge use `--follow-up-of T`. - Judge reject for "insufficient evidence" and no code change asked: spawn a fresh reviewer or QA on the same head with the judge's reason in `--prompt`, then the judge again. No coder (L4). 2. Write the retry brief (L2). The coder's `--prompt` says "attempt N of 3", lists every open blocking finding with its source (reviewer, QA or judge), and says the coder owns the task now. Then `factory spawn coder --task T --prompt -`. 3. Diagnose before the third attempt (L3). When attempt 2 f