parallel-execution

Execute independent sprint tickets in parallel using isolated git worktrees.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/busboom-software-studio/design-trainer --skill parallel-execution-busboom-software-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-execution
Source: https://github.com/busboom-software-studio/design-trainer/tree/main/.claude/skills/parallel-execution
Command: npx skills add https://github.com/busboom-software-studio/design-trainer --skill parallel-execution-busboom-software-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parallel execution of independent sprint tickets by leveraging git worktrees to provide filesystem isolation, enabling faster delivery with opt-in control.

Core Features & Use Cases

  • Analyze ticket independence by verifying that no ticket depends on another and that plans do not list overlapping files to modify.
  • Create a separate git worktree for each eligible ticket to run implementations concurrently while maintaining isolation.
  • Dispatch the implementation for each worktree in parallel and monitor results for tests and acceptance criteria.
  • Review results and merge worktrees back into the sprint branch in a guarded sequence, with fallback to sequential processing for conflicts.
  • Clean up worktrees and branches to avoid dangling resources after the sprint.

Quick Start

Enable parallel sprint execution by analyzing ticket independence, creating a worktree per ticket, dispatching implementations concurrently, and merging changes back to the sprint branch when complete.

Frequently Asked Questions about parallel-execution

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

FAQPage Schema
How do I run sprint tickets in parallel using git worktrees?

Running sprint tickets in parallel with git worktrees involves creating a separate worktree for each independent ticket, dispatching implementations concurrently, and merging the results back into the sprint branch sequentially.

When should I use parallel execution for sprint tickets?

Use parallel execution for multi-ticket sprints where tickets are independent and have no overlapping file changes, enabling concurrent workstreams while preserving filesystem isolation.

How does parallel sprint execution handle merge conflicts?

Parallel sprint execution merges worktrees back into the sprint branch in a guarded sequence, automatically falling back to sequential processing when merge conflicts are detected.

Can I execute sprint tickets concurrently if they modify the same files?

No, concurrent execution requires ticket independence, meaning plans must not list overlapping files to modify to maintain safe workspace isolation across parallel workstreams.

What is the process for cleaning up git worktrees after a sprint?

Cleaning up git worktrees after a sprint involves removing the isolated workspaces and branches to avoid dangling resources after the parallel execution and guarded merging are complete.

Does parallel execution verify tests and acceptance criteria for each worktree?

Yes, parallel execution monitors results for tests and acceptance criteria for each worktree before reviewing results and initiating the safe merge back into the sprint branch.