parallel-step

To run parallel tasks for software development tracks, you orchestrate wave-based dispatch to execute multiple sub-tasks concurrently. This fans out work to specialized subagents simultaneously, maximizing throughput and reducing total development time.

Wave-based parallel task orchestration is a mechanism that dispatches multiple independent sub-tasks concurrently during implementation phases. It manages integration cycles to coordinate specialized subagents while maintaining strict state consistency.

Parallel task execution ensures state consistency during interruptions by using track-state for atomic transitions. This state-machine integration guarantees consistent recovery and atomic task finalization according to the defined wave-step spine.

Yes, orchestrating parallel subagents requires a valid track environment and operates within the Conductor plugin ecosystem. You must adhere to the defined wave-step spine to properly finalize atomic tasks.

You should use concurrent task dispatch when implementing a feature with multiple independent sub-tasks. Fanning out the work to specialized agents simultaneously significantly reduces total development time compared to sequential execution.

Wave-based parallelism requires strict adherence to the defined wave-step spine for atomic task finalization and depends on a valid track environment. It is limited by the Conductor plugin ecosystem and may not suit tasks lacking independent sub-tasks.