worktree-fleetlisted

# Worktree Fleet A skill for running N independent agents in parallel, each isolated in its own git worktree on its own branch. Independence is validated before anything spawns — if two workers declare overlapping `target_files`, the skill refuses with a clear conflict message. ## Decision tree — which fleet? ``` You want to run multiple agents in parallel. Which fleet? 1. Are the tasks independent (no shared files, no shared state)? YES → worktree-fleet ← YOU ARE HERE NO → continue 2. Does the work need iteration with a reviewer making accept/iterate decisions? YES → iterative-fleet NO → continue 3. Is the work a one-shot DAG (each agent runs to completion, dependencies via depends_on)? YES → dag-fleet NO → continue 4. None of the above? → You're the orchestrator. Open multiple Claude Code sessions. ``` ## When to use THIS skill - Tasks touch **non-overlapping files** (different modules, different docs, etc.) - You want **merge-safe isolation** — each worker on its own branch, no mid-flight conflicts possible - The merge decision is **yours** — after workers complete, you choose merge order / strategy - You want **independent branches** in git that you can inspect, cherry-pick, or discard ## When NOT to use this skill - Workers need to coordinate or read each other's output → `dag-fleet` with `depends_on` - Tasks overlap files (even partially) → fix the task split first, then come back - You want headless workers + reviewer-in-loop → `iter