Summary
Add a low-risk acceleration path for serial sprint execution by prewarming the next issue's worktree and dependency setup while the current issue is already past developer editing and is in the review/merge tail.
Why
We want throughput gains without parallelizing developer execution or increasing merge-conflict risk. Worktree creation and setup are preparatory steps that can overlap safely with non-editing tail work.
Proposed approach
- Keep developer execution and merge ordering strictly serial.
- During the current issue's late review/merge window, create the next issue worktree in advance.
- Optionally run the configured worktree setup/validation commands early.
- Re-verify branch provenance when actual execution starts so prewarming never reintroduces stale-branch reuse.
Acceptance criteria
- Serial developer execution semantics remain unchanged.
- Next issue worktree/setup can be prepared ahead of time.
- If prewarm fails, execution falls back cleanly to the current inline setup path.
- Tests cover the prewarm happy path and fallback path.
Summary
Add a low-risk acceleration path for serial sprint execution by prewarming the next issue's worktree and dependency setup while the current issue is already past developer editing and is in the review/merge tail.
Why
We want throughput gains without parallelizing developer execution or increasing merge-conflict risk. Worktree creation and setup are preparatory steps that can overlap safely with non-editing tail work.
Proposed approach
Acceptance criteria