run-phase

An automated build-review-fix cycle orchestrates builder and reviewer agents to iterate on a software phase, looping until the review passes or user intervention is required. It coordinates handoffs automatically to ensure safe, auditable progress.

Orchestrating agents for iterative phases coordinates builder and reviewer handoffs across functional spec, mock build, and real integration scenarios. It loops through automated re-runs and user prompts on failure to enforce phase detection and auditable progress.

Automated phase orchestration works across Flutter-based dashboard widgets, panels, and runners with phase-aware routing. It coordinates the builder and reviewer agents through the build-review-fix cycle for these specific component kinds.

During automated orchestration, a failed phase review triggers automatic re-runs and user prompts. The system loops the builder and reviewer agents until the phase passes, while recording logs and guardrails to ensure safe, auditable progress.

Yes, you need to provide the phase number and the path to the spec or app to begin the automated build-review workflow. This input initializes the cycle and routes the agents through the functional spec, mock build, or real integration phases.

You should manually intervene in an automated build-review-fix loop when the reviewer agent fails and prompts for user input. The orchestration stops looping and awaits your decision to ensure safe, auditable progress when automated re-runs cannot resolve the failure.