1---2name: parallel-worktree-supervisor3description: plan and supervise low-overlap parallel work across git worktrees or stacked branches. use when a backlog could be split safely, when multiple small dependent changes need reviewable sequencing, or when merge-blocking risks must be made explicit before parallel execution.4---56# Parallel Worktree Supervisor78## Trigger Signals910- the backlog could be split into low-overlap tracks with clear ownership boundaries11- multiple small dependent changes need stacked review instead of one giant branch12- the team wants explicit merge blockers, rebase rules, and validation gates before parallel execution1314## Inspect First1516- task list or issue graph, including dependencies and shared prerequisites17- repo hotspots such as root config, lockfiles, generated artifacts, migrations, and shared contracts18- code ownership, test entrypoints, and branch protection or merge expectations19- whether worktrees, stacked branches, or plain feature branches are already in use2021## Workflow22231. map tasks by dependency, risk, and shared-file overlap242. carve the work into tracks that minimize contention on root config, generated files, and public contracts253. assign a branch or worktree plan with base branch, stack order, and merge blockers264. define rebase cadence, validation gates, and when a track must pause for another track to land275. report status in terms of ready, blocked, risky overlap, or merge-ready2829## Output Contract3031- sharding plan with branch or worktree names and ownership notes32- explicit dependency graph and merge order33- overlap hotspots and the files or contracts that make them risky34- validation and rebase expectations for each track3536## Failure Modes3738- hidden coupling means the work is not actually independent enough to parallelize39- the repo relies on shared generated files, lockfiles, or root config that every track must touch40- there is no trustworthy validation path to catch skew between branches4142## Escalation4344- escalate when a schema, API, or root-build change affects multiple tracks at once45- escalate when stacked branches become too interdependent to review independently46- escalate when branch protection, review ownership, or release timing constraints are unclear4748## References4950- `skills/parallel-worktree-supervisor/references/task-sharding-rules.md`51- `skills/parallel-worktree-supervisor/references/worktree-operations.md`52- `skills/parallel-worktree-supervisor/references/stacked-diffs-and-review.md`53- `skills/parallel-worktree-supervisor/references/merge-readiness.md`54- `skills/parallel-worktree-supervisor/references/output-template.md`55- `skills/parallel-worktree-supervisor/references/examples.md`
ldilov