pickup

Multi-agent task execution without branch conflicts is coordinated by identifying unclaimed sprint tasks and proposing a two-phase isolation plan for user approval before making changes. This propose-then-execute workflow detects active worktrees and branches to present safe isolation recommendations.

To select the next unclaimed task in a sprint wave, the system scans your PLAN.md file to identify available tasks. It then evaluates the current landscape of active worktrees and in-flight work to propose the optimal task for execution.

The propose-then-execute workflow for task isolation is a two-phase process where the system first recommends a worktree path and execution steps, then waits for user approval before changing the working state. This minimizes conflicts in multi-agent environments by ensuring safe concurrent work.

Yes, you can batch tasks within a sprint wave to optimize throughput and coordination. The system identifies batch opportunities during the proposal phase, allowing multiple related tasks to be grouped for safe concurrent work within isolated git worktrees.

Yes, this task management approach requires tracking work in PLAN.md waves, branches, and worktrees. It is designed specifically for multi-agent software projects that use this structure to manage sprints and requires user approval before changing the working state.

You should not use an automated task isolation proposal if your software project does not track tasks in PLAN.md waves or use git worktrees. The mechanism relies on detecting active worktrees and branches to formulate safe execution paths for multi-agent environments.