bmad-parallel

Parallelizing BMAD story tasks involves automatically detecting independent tasks and spawning dedicated agents for each. The process creates isolated worktrees and branches to execute tasks concurrently, then merges results back into the main branch.

Isolated worktree creation in concurrent agent execution works by assigning each parallelizable task its own worktree and branch. This guarantees task isolation and clean merges while agents execute concurrently.

BMAD parallel execution requires no specific dependencies or components. It operates within a BMAD-enabled project, automatically detecting parallelizable story tasks and spawning agents without external dependencies.

Automated agent orchestration is designed for stories with multiple independent tasks. It spawns separate agents to handle each task concurrently, so dependent tasks requiring sequential execution are not suitable for this parallel approach.

Clean merge failures in parallelized BMAD story tasks can occur if task isolation is compromised. The skill manages per-task logs and branches to ensure transactional consistency and TASK_COMPLETE signaling, preventing merge conflicts.

The best way to manage per-task logs and branches during parallel story execution is through the skill's built-in orchestration. It automatically handles per-task logging and branch management, ensuring transactional consistency during merges.