What problem does it solve? Running an unattended backlog loop requires a disciplined foreman that never picks work itself, never answers approval gates, and never trusts worker claims without evidence. This Skill automates one safe iteration of that loop: watch the queue, dispatch one card, collect verified results, and report. ## Core Features & Use Cases - Queue Watching: Arms a persistent checksum-based monitor on the backlog file so each change triggers a new idempotent iteration. - Isolated Dispatch: Spawns exactly one write-capable worker per card in its own git worktree, with a fixed-field dispatch block and standing orders (branch rename, lane-local verification, evidence file, no push). - Evidence-Based Completion: Advances a card only after reading verbatim passing output in the worker's evidence file; missing or stale evidence leaves the card picked and reported. - Hard Boundaries: Never adds or picks backlog items, never answers approval gates, never pushes, merges, or deletes branches — blocked decisions are surfaced to the operator. - Use Case: An operator backgrounds a Claude Code session running a bare /loop; the foreman continuously works through operator-picked backlog cards overnight, leaving a report naming branches, worktrees, and blocked decisions for morning review. ## Quick Start Run a bare /loop in the project session and background it so the kanban foreman iterates over the picked backlog queue unattended.
