dag-fleet

# Fleet A skill for running parallel `claude -p`, `codex exec`, or `pi -p` workers in tmux with budgets and DAG dependencies. Supports Claude, Codex, and Pi providers — set per-fleet or per-worker. Operator owns all kill / steer / re-direction — there is no auto-restart, no auto-verify, no babysitter loop. ## Prerequisites - **bash >= 4.0** — macOS ships bash 3.2 (from 2007). Install modern bash: `brew install bash` - **flock** — Linux built-in. macOS: `brew install flock` - **tmux** — `brew install tmux` or `apt install tmux` - **jq** — `brew install jq` or `apt install jq` ### macOS quick-start ```bash brew install bash tmux jq flock # Then invoke launch.sh explicitly with bash 4+: /opt/homebrew/bin/bash /path/to/dag-fleet/scripts/launch.sh <fleet-root> ``` If `flock` is unavailable, `launch.sh` will skip locking with a warning. Pass `--no-lock` to suppress the warning. ## When to use this skill (and when NOT to) **FIRST: prefer Claude Code's built-in Agent tool when any of these are true.** It's simpler, faster, and avoids the fleet machinery entirely. - The work fits inside the current conversation - All sub-agents will finish in under 10 minutes - You'll synthesize the results in the same session - You don't need budget caps or dependency ordering **Reach for THIS skill only when ≥1 of these is true:** - **Persistence:** the run will outlive the parent `claude` process (e.g. multi-hour fleet, user closes laptop) - **Per-worker budgets:** you need `max_budget_usd...