parallel-issues

You can execute multiple GitHub issues in parallel safely by applying dependency graphs and zero-conflict waves to orchestrate work across multiple worktrees. This prevents cross-issue file overlaps by generating per-issue AUTO-mode worker prompts for concurrent execution.

Dependency-aware wave planning is a technique that analyzes file overlaps and dependencies across multiple GitHub issues to orchestrate conflict-free execution waves. It ensures that only non-overlapping tasks run concurrently, generating AUTO-mode prompts and monitoring completion across each wave.

Start a parallel run by specifying issue ranges and pane limits, such as using a command like /parallel-issues 732-743 --panes 4. This initiates a four-pane concurrent execution, generating worker prompts and orchestrating safe, conflict-free waves across the selected issues.

Parallel issue execution supports a limited number of panes for concurrent worktree management. The system implements robust error handling and ensures all changes ship via a /ship command when criteria are met, accommodating pane constraints during wave orchestration.

The best way to monitor completion across parallel GitHub issue waves is to use end-to-end execution monitoring that generates a completion report. The system ensures all changes ship via a /ship command when criteria are met, providing robust error handling throughout the process.

You should avoid running GitHub issues in parallel waves when issues have heavy file-level dependencies and overlaps that cannot be separated into zero-conflict waves. The system's dependency analysis prevents cross-issue conflicts, but highly interdependent tasks may require sequential execution.