worktree-parallel

Automate isolated git worktree setup, synchronization, quality gates, and cleanup.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill worktree-parallel-tmalcolm-0607
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-parallel
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/worktree-parallel
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill worktree-parallel-tmalcolm-0607

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing parallel development across multiple software milestones often leads to file conflicts, branch chaos, and environment clashes when teams try to work on features concurrently without proper isolation.

Core Features & Use Cases

  • Automated Parallel Worktree Setup: Creates isolated git worktrees for each selected milestone, each with its own dedicated branch and linked shared project infrastructure like rules and specs.
  • Isolation & Verification: Enforces disjoint port ranges, independent dependency restores, and link integrity checks per worktree to prevent cross-milestone interference.
  • Safe Lifecycle Management: Handles quality gate execution per worktree and provides safe cleanup workflows that remove links before deleting worktrees to avoid accidental deletion of shared project content.
  • Use Case: A team implementing milestones 018, 019, and 024 concurrently can use this skill to spin up isolated worktrees for each, run tests independently, and merge changes without conflicts.

Quick Start

Use the worktree-parallel skill to set up isolated parallel git worktrees for your selected milestones with linked project infrastructure and independent dependency restores.

Frequently Asked Questions about worktree-parallel

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

FAQPage Schema
How do I set up isolated git worktrees for parallel multi-milestone development?

Git worktrees for parallel development are provisioned by creating isolated branches per milestone with linked shared project infrastructure, enforcing disjoint ports and independent dependency restores to prevent cross-milestone interference.

What's the best way to prevent merge conflicts and environment clashes when working on multiple milestones concurrently?

Preventing merge conflicts and environment clashes requires isolated parallel worktrees that enforce disjoint port ranges, independent dependency restores, and link integrity checks per milestone to eliminate cross-branch interference.

How does safe cleanup work for parallel git worktrees with linked project infrastructure?

Safe cleanup for parallel worktrees removes linked project infrastructure references before deleting the worktrees, preventing accidental deletion of shared project content like rules and specs during the removal process.

Can I run independent quality gate execution and tests for each git worktree?

Quality gate execution runs independently per worktree, allowing teams to run tests and verification checks for each milestone in isolation without interference from other parallel development branches.

Does branch isolation with git worktrees support concurrent development of milestones 018, 019, and 024?

Branch isolation supports concurrent milestones by spinning up dedicated worktrees for each milestone with separate branches, disjoint port ranges, and independent dependency restores for conflict-free parallel development.