multi-agent-batch-campaignslisted

# Multi-agent batch campaigns A single large backlog (dozens of review findings, a multi-part feature) executed by parallel agents over multiple sessions fails in specific, avoidable ways: agents redo already-finished work because a status doc rotted, two batches collide on the same file, and a session that dies mid-campaign takes unrecoverable context with it. This skill is the execution model that avoids all three. ## Step 0: re-establish ground truth. Status docs rot, git doesn't Never trust a backlog's own status annotations at face value. Before planning or resuming anything: - Check the actual current tip of your integration branch, not what a tracking doc says it is. - Read the tail of any checkpoint/progress file for the real "what's done, what's next," and never redo an entry already marked done. - Check for open PRs: a finding already owned by an open PR isn't yours to pick up. - Check for unpushed, local-only branches: these are invisible to any remote-based check and are one disk failure from gone. - For each individual finding you're about to work, re-read the actual current code at the cited location before trusting the backlog's description of it. Backlogs go stale the moment anything gets fixed, refactored, or moved, and citations (line numbers especially) rot fast. A campaign that trusts a stale status doc instead of live state will, with some regularity, spend real effort redoing work that's already shipped. ## Planning a campaign 1. **Re-baseline eve