afk-loop
Run this loop per /supervise: you plan, dispatch, and merge — investigators, implementers, reviewers, QA agents, and fixers do everything else. The PR is the durable store — findings, logs, and ledgers live there as comments — and each PR's AFK summary is its state file. The numbered steps are pipeline stages, not phases: each issue advances the moment it's ready. Each invocation is one pass.
Brief sub-agents with context pointers — the issue, the PR, prior comments — never with the content itself; what a pointer reaches needs no restating.
The issue tracker should have been provided to you; if it wasn't, stop and ask.
Settings
Three settings govern the loop — /afk-loop [merge-mode] [concurrency] [cap]. Take each from the invocation; a default applies silently when the invocation omits its setting.
- Merge mode — you merge clean PRs yourself, or park them for a human to merge. No default — ask (
AskUserQuestion, before planning). - Concurrency — how many issues run in flight at once. Default 5.
- Cap — how many fix attempts an issue gets before you stop it. Review rounds, QA rounds, and check-fix attempts are counted separately, each capped at this number. Default 5.
Every setting holds for the whole loop.