parallel-workers

You can run multiple coding tasks in parallel by spawning isolated workers, each operating in its own git worktree with a separate branch. This eliminates cross-task interference and tracks progress through state stages until PR merge.

Automating concurrent feature development with git worktrees involves spawning workers per task, tracking their lifecycle states, and enforcing pre-merge validations. This skill manages worktree creation, branch isolation, and PR integration automatically.

You track parallel worker status by using a state tracker script to query specific worker IDs. The system manages worker states across implementation stages, from spawn through PR review to final merge.

Yes, you need GitHub CLI installed because this skill depends on it, alongside git and yaml, to automate PR workflows, enforce pre-merge validations, and clean up merged workers across isolated worktrees.

Yes, you can automatically clean up git worktrees after a task is merged by running the worker manager cleanup command with the merged state flag, removing isolated branches and associated worktrees.

You should use isolated git worktrees for parallel execution when independent SDLC tasks require simultaneous implementation and testing. Worktrees prevent file conflicts between concurrent branches, accelerating delivery via isolated PR workflows.