looplisted

# /loop ## Goal Run a mission as a bounded series of attempts: pick one idea, make exactly one change, grade it, keep or discard, and stop at a hard cap, a per-attempt timeout, or two consecutive GATE failures (circuit breaker) — never on trust alone. All mechanical enforcement (state, ledger, cap, breaker) lives in `core/infra/loop-run.sh`; this skill is the iteration protocol that calls it. ## Relationship to skills/harness-loop This skill is the generic protocol: fresh context per iteration, exactly one task per iteration, resumable on-disk state, hard budget. `/harness-loop` is a SPECIALIZATION of it for one fixed mission — improving this harness's own reviewer prompts under §5's rules (fixed TARGET regex, GATE floor, branch convention). If the mission is "improve the harness itself", follow `/harness-loop` instead of the generic steps below — its numbered procedure is the maintained regulation for that mission. ## Steps 1. **Mission intake.** From the request, determine: a slug (short, kebab-case), a TARGET file-path regex the loop may edit, a base ref (the mission's starting commit — usually HEAD), an attempt cap (default 5), and a per-attempt timeout in seconds (default 600). Confirm any ambiguous one with the user — a loop whose edit scope isn't pinned down is not this skill's contract. 2. **Initialize.** ```bash bash core/infra/loop-run.sh init <slug> --target '<regex>' --base <ref> \ [--cap N] [--timeout-s N] --mission "<one-line des