parallel-phases

Orchestrates multi-task parallel agent execution across git worktrees with review and merge gates.

599|54|Updated Aug 21, 2025
One-click install
npx skills add https://github.com/ZacheryGlass/.claude --skill parallel-phases
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-phases
Source: https://github.com/ZacheryGlass/.claude/tree/main/skills/parallel-phases
Command: npx skills add https://github.com/ZacheryGlass/.claude --skill parallel-phases

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating multiple independent coding tasks by hand is slow and error-prone: agents duplicate discovery work, branches conflict at merge time, and long-running work loses progress when the session is cleared. This Skill automates the full lifecycle of parallel multi-task work, from planning through merged, tested, documented results.

Core Features & Use Cases

  • Planning phase: Gathers code intelligence, analyzes merge-conflict risks, groups tasks into maximally parallel phases, and writes self-contained agent prompts plus PLAN.md and STATE.md files.
  • Autonomous execution phase: Dispatches Opus agents in isolated git worktrees, runs a per-task review gauntlet with auto-fix commits, merges each phase behind a test gate, and finishes with a documentation-update agent.
  • Crash-safe state management: All state lives in file-backed storage outside the repo, so work resumes cleanly after /clear or session restarts, with hard-exit BLOCKED conditions for human intervention.
  • Use Case: You have five independent refactoring and feature tasks for a repo. Run the skill once to generate an approved plan, then let it dispatch agents in parallel worktrees overnight, review and fix each diff, merge phases behind test gates, and update docs.

Quick Start

Ask the assistant to run the parallel-phases skill to plan and execute your list of independent tasks in parallel worktrees with automated review and merging.

Frequently Asked Questions about parallel-phases

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

FAQPage Schema
How do I run multiple coding tasks in parallel with AI agents?

Invoke the parallel-phases skill with your task list. It analyzes dependencies and merge-conflict risks, groups tasks into parallel phases, then dispatches agents in isolated git worktrees so they execute concurrently without interfering.

How does the skill prevent merge conflicts between parallel agents?

During setup it analyzes file-level overlap between tasks and applies mitigations: designating a build-config owner, combining conflicting tasks, or serializing them into separate phases. Each phase merges through an integration branch behind a test gate.

Can parallel agent work resume after clearing the conversation?

Yes. All state lives in files under ~/.claude/parallel-phases/<project-hash>/, outside the repo. Re-running the skill recomputes the state directory and resumes from STATE.md, picking up exactly where execution left off.

What happens when a parallel task fails its review or tests?

The review gauntlet fixes Critical and Should-Fix findings automatically on the task branch. If a reviewer reports BLOCKED, a merge conflict occurs, or the phase test gate fails, the skill appends a BLOCKED line to STATE.md and exits until a human resolves it.

Does parallel-phases require a git repository?

Yes. The skill hard-exits if the working directory is not a git working tree, because worktree isolation is mandatory for parallel code-modifying tasks. Each task runs on its own branch in its own worktree.

When should I not use parallel task orchestration?

Avoid it for a single small change, tasks with heavy file overlap that cannot be mitigated, or work requiring interactive decisions mid-task. Per-phase overhead (review, fix, merge, test) only pays off for tasks of roughly 30 minutes or more of agent work.