worktrees:orchestrator

Coordinate parallel development across subagents using isolated git worktrees.

4|1|Updated Jan 23, 2026

Search Tags:#git #worktrees #subagents #branch-management #orchestrate #parallel-development

Ready to run

npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill worktrees-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktrees:orchestrator
Source: https://github.com/aaronbassett/aaronbassett-marketplace/tree/main/plugins/worktrees/skills/orchestrator
Command: npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill worktrees-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of coordinating multiple subagents across isolated git worktrees to enable parallel development, reducing conflicts and handoff friction.

Core Features & Use Cases

Orchestrates a main agent with multiple subagents operating in separate worktrees
Creates and tracks worktrees for feature branches, manages progress, and ensures orderly merges
Use Case: Decompose a feature into independent tasks and run them in parallel across worktrees while keeping state isolated

Quick Start

Invoke the orchestrator with a feature name to begin coordinating parallel development. Create per-feature worktrees using git worktree add commands, monitor progress with git worktree list and commit logs, and merge results in dependency order before cleanup.

Frequently Asked Questions about worktrees:orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate parallel subagents using git worktrees?▼

To coordinate parallel subagents using git worktrees, an orchestrator creates and manages separate worktrees for each subtask, enabling isolated execution. It tracks progress and merges results in dependency order before cleanup.

What is the best way to run parallel development tasks without git branch conflicts?▼

Running parallel development tasks without git branch conflicts is best achieved by using isolated git worktrees for each feature. This orchestrator creates separate worktrees for subagents, keeping state isolated and ensuring orderly merges.

How does git worktree orchestration work for feature branch management?▼

Git worktree orchestration works by creating a main agent that manages multiple subagents in separate worktrees. It handles feature branch creation, progress tracking via commit logs, and merges results sequentially before cleaning up.

Do I need existing feature branches to start orchestrating parallel worktrees?▼

You do not need existing feature branches to start orchestrating parallel worktrees. You invoke the orchestrator with a feature name, and it creates per-feature worktrees dynamically using git worktree add commands.

How do I clean up git worktrees after merging parallel subagent tasks?▼

To clean up git worktrees after merging parallel subagent tasks, the orchestrator merges results in dependency order and then performs worktree cleanup. It monitors progress with git worktree list before safely removing isolated environments.