parallel-execution

Execute parallel sprint tickets by creating isolated git worktrees for each independent ticket. This approach dispatches implementations concurrently while preserving filesystem isolation and allowing independent review of results.

Isolate parallel sprint work by creating a separate git worktree for each eligible ticket. This ensures filesystem isolation so concurrent implementations do not conflict, while still allowing independent review of each result.

No, parallel ticket execution requires each ticket to be strictly independent. Tickets with dependencies do not qualify for this concurrent workflow and must be handled sequentially to avoid conflicts.

Yes, you need an active sprint lock, access to git worktrees, and a mechanism to dispatch work concurrently. These three prerequisites are required before opting into parallel ticket execution.

Avoid parallel execution if your tickets have dependencies, lack an active sprint lock, or if your team has not explicitly opted in. Use the safe sequential fallback when native parallel flows are unavailable.