From git-worktrees
Creates isolated git worktrees for parallel feature development and executes identical plans across workspaces via subagents for concurrent experimentation and result comparison.
npx claudepluginhub henkisdabro/wookstar-claude-pluginsThis skill uses the workspace's default tool permissions.
Enable parallel feature development by creating isolated git worktree directories, then executing the same plan across multiple workspaces simultaneously.
Sets up and manages Git worktrees for isolated feature branches, parallel development, hotfixes, and subagent tasks. Includes safety checks, naming conventions, dependency installs, and independent testing.
Creates and manages git worktrees for parallel coding sessions during tests, builds, branch switching, or exploring multiple approaches.
Creates isolated git worktrees as sibling directories for parallel branch development, keeping main repo clean. Use for new features, fixes, or experiments needing isolation from main/master.
Share bugs, ideas, or general feedback.
Enable parallel feature development by creating isolated git worktree directories, then executing the same plan across multiple workspaces simultaneously.
Create N isolated worktrees for parallel development:
# Create worktree directory
mkdir -p trees
# Create worktrees (example: 3 parallel workspaces)
git worktree add -b feature-1 ./trees/feature-1
git worktree add -b feature-2 ./trees/feature-2
git worktree add -b feature-3 ./trees/feature-3
# Verify worktrees
git worktree list
Each worktree is a complete, isolated copy of the codebase. All worktrees share git history but have independent working directories.
Launch N subagents (one per worktree) using the Task tool:
Example Task invocation:
Use the Task tool to launch a general-purpose agent with:
- prompt: "Working in trees/feature-1, implement [plan]. Write a RESULTS.md summarising changes."
- run_in_background: true (for parallel execution)
git worktree remove ./trees/feature-1
git worktree prune
git cherry-pick feature-2
# or merge the branch
git merge feature-2
project/
├── trees/
│ ├── feature-1/ # Worktree 1 (full codebase copy)
│ │ └── RESULTS.md
│ ├── feature-2/ # Worktree 2 (full codebase copy)
│ │ └── RESULTS.md
│ └── feature-3/ # Worktree 3 (full codebase copy)
│ └── RESULTS.md
└── (main working directory)
Each agent should produce a summary in this format:
# Results - [Feature Name]
## Changes Made
- List of files modified/created
- Summary of approach taken
## Key Decisions
- Design choices made
- Trade-offs considered
## Testing Notes
- How to verify the implementation
- Known limitations