execute-phase

To run phase tasks in parallel, you can invoke the execute-phase command with a specific phase number, which automatically spawns multiple coder agents concurrently for all eligible tasks and updates progress.json upon completion.

Tracking development phase progress is handled by reading and updating progress.json, which marks tasks as completed or blocked, recalculates phase progress, and provides an overall summary to keep your plan on track.

Parallel task execution handles blocked tasks by automatically filtering them out from the active execution queue and reporting the specific blockers to the user for manual resolution.

Yes, you can execute a specific phase by providing the phase number directly as input, which bypasses interactive selection and immediately starts spawning coder agents for that phase.

Agents scale during execution by spawning different types of coder agents, such as small-coder and high-coder, concurrently according to the specific task complexity defined within the chosen phase.

Interactive phase selection appears when you invoke the execution command without providing an explicit phase number, triggering an AskUserQuestion prompt to let you choose the desired phase.