execution-manager

Create isolated git worktrees and tmux sessions for parallel sub-coordinators.

Updated Dec 9, 2025

Search Tags:#automation #tmux #git worktree #parallel #coordination

Ready to run

npx skills add https://github.com/blueif16/amazing-claude-code-plugins --skill execution-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execution-manager
Source: https://github.com/blueif16/amazing-claude-code-plugins/tree/main/infistack/skills/execution-manager
Command: npx skills add https://github.com/blueif16/amazing-claude-code-plugins --skill execution-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Uses git worktrees to scaffold and manage tmux sessions for parallel sub-coordinators, initializing mini-PRD, acceptance criteria, branch names, and workspace paths.

Core Features & Use Cases

Worktree-based parallelism: Create isolated worktrees per section.
Tmux session management: Launch and manage dedicated sessions per part.
Sub-coordinator bootstrap: Initialize mini-PRD, acceptance criteria, and workspace details in each session.
Monitoring & cleanup: Track completion signals and perform cleanup after completion or failure.

Quick Start

For each section, run the provided commands to create a worktree, start a tmux session, and launch Claude resume in that session.

Frequently Asked Questions about execution-manager

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

FAQPage Schema

How do I run multiple git worktrees in parallel with tmux?▼

Parallel orchestration with tmux creates isolated git worktrees per section using git worktree commands, launches dedicated tmux sessions for each, and initializes sub-coordinators with branch names and workspace paths. Each session runs independently while a parent process monitors completion signals.

What's the best way to coordinate multiple tasks across git branches simultaneously?▼

Multi-section orchestration uses git worktrees to isolate each branch, tmux sessions to manage parallel execution, and sub-coordinators to handle per-section work. This approach eliminates branch conflicts, automates startup, and tracks status (COMPLETE/WAITING/ERROR) across all sections.

Can I automate spawning isolated workspaces for parallel development tasks?▼

Automated workspace creation scaffolds git worktrees with isolation per section, launches tmux sessions with dedicated terminals, bootstraps sub-coordinators with mini-PRD and acceptance criteria, and performs cleanup after completion or failure.

How do I monitor and clean up parallel tmux sessions after tasks complete?▼

Status polling tracks COMPLETE, WAITING, and ERROR signals from each tmux session, then executes cleanup routines to remove worktrees and sessions once all sections finish or fail, ensuring no orphaned resources remain.

Do I need separate git branches for running parallel work on the same project?▼

Yes. Git worktrees require separate branches per section (created with -b {section-id}) to isolate parallel changes. This prevents conflicts and allows independent commit histories while tmux sessions orchestrate execution across branches.

What happens if one parallel section fails during orchestration?▼

Sub-coordinator status signals ERROR for failed sections. The orchestration monitors this state, performs cleanup of affected worktrees and tmux sessions, and halts or escalates based on your failure-handling logic.