loop-nanny

Monitor, triage, and clean up after agent loops. The agent-loop skill starts loops. This skill keeps them healthy.

Poll every 2–3 minutes. A story typically takes 3–8 minutes (test-write → implement → review → judge). If a story shows no progress for 10+ minutes, something is stuck.

| ✅ PASS | Story completed | None | | ⏭ SKIP | Exhausted retries | Check if code landed anyway (common — see Skip Triage) | | ▶ STORY.DISPATCHED | Implementor running | Wait | | ▶ TESTS.WRITTEN | Reviewer running | Wait | | ▶ CHECKS.COMPLETED | Judge evaluating | Wait | | ▶ STORY.RETRIED | Failed, retrying | Check attempt output for patterns |

Monitor running agent loops, triage failures, clean up after completion, and decide when to intervene. Use when a loop is running and needs babysitting, when a loop just finished and needs post-merge verification, when stories are skipping/failing and need diagnosis, or when stale test artifacts need cleanup. Triggers on: 'check the loop', 'what happened with the loop', 'loop finished', 'clean up after loop', 'why did that story skip', 'monitor loop', 'nanny the loop', or any post-start loop management task. Distinct from agent-loop skill (which handles starting loops). Source: joelhooks/joelclaw.