worktree-fleet

What problem does it solve?

worktree-fleet prevents parallel agent edits from colliding by isolating each worker in its own git worktree and branch, then validating that workers do not overlap on the files they claim to touch.

Core Features & Use Cases

• Independence validation before spawning: the skill refuses to launch when any two workers’ declared target_files overlap (including glob overlap), protecting you from irreversible merge conflicts.
• Merge-safe parallel execution: each worker runs on its own branch/worktree (claude -p, codex exec, or pi -p) so changes are independently captured and inspectable.
• Operator-controlled merging: after completion, you generate a merge plan and manually merge according to the constraints of parallel work.

Use when: refactoring multiple modules at once, updating separate docs, or making concurrent changes across non-overlapping parts of a repo where you still want git history and clean separation.

Quick Start

Launch a merge-safe parallel fleet by creating a fleet.json with distinct target_files per worker, writing a prompt.md for each worker, then running bash ${AGENTS_SKILLS_DIR}/scripts/launch.sh /absolute/path/to/fleet-root.