/loop (bro)

All mechanics live in the bro CLI. This skill is policy only. bro flow next schedules one bead; bro flow loop runs the queue to exhaustion — claim → worktree → agent → push onto the gate stack → repeat — with no per-item "should I continue?" The backlog's existence is the approval.

Configure the agent once

Prefer the provider lane — a providers.<name> registry entry resolves the spawn exactly like bro fleet agents up: