wave-resumelisted

Use when a running wave was interrupted part-way — a crash, a closed window, a machine that went away — and it has to be picked up where it stopped. Reads the wave's own plan file, compares it against the working copies still on disk, the results the agents left behind, and the pull requests that have already merged, brings the tracker back in step with reality, and re-runs only the work that is genuinely still outstanding. Triggers on "resume wave <slug>", "the coordinator died — pick up wave <slug>", "reconcile and resume".
formtrieb/flotilla · ★ 3 · AI & Automation · score 69

Install: claude install-skill formtrieb/flotilla

# wave-resume Reconstruct a wave's state after a Coordinator kill and resume it. The pure reconciler (`resume()`) reads three durable homes — the **spine** (WAL authority), the **live agent worktrees**, and the **on-disk sidecars** (reports/verdicts) — and returns a per-row `adopt`/`redispatch`/`keep`/`needs-attention` decision + a coarse rung. The `{{wave-cli}} resume` subverb then **crash-cleans every `redispatch` row** — unlocks + removes any stale worktree still checked out on that row's branch and deletes the stale branch itself — before printing, so a re-dispatch never collides with leftover debris from a crashed attempt (FOR-10; a dirty crashed worktree is never destroyed silently — see step 4). The skill then applies a **4th, skill-only input the pure reconciler cannot reach**: a PR-merge done-reconcile — a row whose PR merged during the kill is landed `done` via the existing `issue-store close` verb, **ticking the reviewer-met ACs it carries** (`--acked`, derived per-row from the FINAL Reviewer verdict via the engine's `verdict-acked` verb, FOR-17 — the same wire `wave-close` uses; on a no-integration `states.doneState` workspace this fires the FOR-13 fallback), and a closed-unmerged PR is flagged `needs-attention`. It idempotently re-projects the coarse ledger onto the tracker — and does **all of this BEFORE any re-dispatch**. Load **wave-shared** by name first — it owns the auth-preflight / atomic-spine conventions this skill obeys (every tracker write goes throu