specdo-subagent-development

Multi-task development within one active change is coordinated by wrapping independent tasks under a single execution flow, enforcing consistent gating and a consolidated evidence trail. This approach ensures per-task tracking and unified implementation events.

A resolved active apply payload provides the required task scope, handoff payload, gate history, and invocation source needed for subagent coordination. You need it to enforce complete apply context before advancing multiple tasks.

To maintain an evidence trail during parallel tasks, the coordination process records changed files and executed commands per task, then appends an implementation event to the gate history for reliable auditing and routing.

Multi-task subagent coordination does not work without prior task resolution. It strictly enforces required inputs by consuming a resolved active apply payload from upstream processes to ensure complete apply context.

Routing a consolidated implementation to code review or debugging is determined by appending an implementation event to the gate history. This event evaluates the outcome to advance the workflow to the appropriate next step.

The best way to batch independent development tasks is using a wrapper coordination mechanism that executes multiple tasks within a single active change, emitting a unified implementation event while maintaining per-task evidence for auditing.