orchestrator

You can coordinate an asynchronous development workflow using a non-blocking, event-driven model that manages phase transitions through workflow-continue hooks and shared state tracking. This enables seamless handoffs across design, develop, review, and QA phases.

Non-blocking phase orchestration works by using workflow-continue hooks to trigger phase transitions in response to user interactions. A shared workflow state tracks progress across design, develop, review, and QA without halting execution.

You initialize an automated development workflow by running the work-manager.sh init-workflow command with parameters for task ID, branch, platform, worktree, and description to set up the initial state.

Yes, you can track the current state of your asynchronous development workflow by running the work-manager.sh get-workflow command to retrieve the shared workflow status across all active phases.

You start a specific phase in the automated workflow by running the work-manager.sh start-phase command with the target phase name and the agent task ID to trigger the phase transition.

The best way to handle error checking during development automation is using an orchestration protocol that enforces automatic status checks, error handling, and command utilities to manage end-to-end workflow transitions safely.