← ClaudeAtlas

orchestratelisted

Use when bounded fan-out, multi-agent research, cross-family review, parallel audits, Herdr control, or autonomous ready-issue implementation helps. Not for tiny work, coupled debugging, or run-until-STOP jobs; use diagnose or autopilot.
mblauberg/provenant · ★ 2 · AI & Automation · score 68
Install: claude install-skill mblauberg/provenant
# Multi-agent orchestration ## Overview Decompose -> waves -> reduce -> gate. ## Rules - **Use parallel fan-out only after the decomposition/value gate passes.** - Preflight dependencies/shared errors. - **No concurrent shared-state writes.** Partition authorised writers into repository `.worktrees/<task-agent>`; otherwise use a serial applier. - Parallel lanes stop ready-to-merge. The chair merges serially, refreshes the next branch from current main, then reruns checks and reviews after commit/tree changes. - **Keep topology exact.** One chair; leaders settle recursive obligations. Handoff is a generation-bound operator action. - **Answer-bearing external work uses Fabric request/reply; Herdr only wakes.** Pane injection is fire-and-forget steering. Without callback, record `FABRIC-ROUNDTRIP-UNAVAILABLE` and collect an artifact. - Record worker cwd; never assume repository. - **Workers write full output to files**; return a digest/path. - **Liveness: size proves nothing.** Compare CPU and session-log mtime; see `worker-liveness.md`. A detached task is not dead: check the PID before reusing a worktree. - **Cross-family follows the HARNESS risk ladder.** Targeted lenses plus other primary; distinct family when available; record terminal skips. - **Objective checks outrank opinions. You own the final call.** - Discover current model/tool options at runtime. ## When This Pays Before parallel dispatch, require independent information or artefacts; stable