omc.team

Team orchestration with review-first verification blocks faulty changes from progressing to tests by requiring clean review outcomes before any test execution runs. This prevents unreviewed code from advancing through workflow iterations.

Review-first task orchestration is a workflow mechanism that gates task progression on completed code reviews before allowing tests or deployments. You need it when coordinating multi-person feature tasks across iterations to prevent unreviewed changes from advancing.

Run team orchestration by issuing a CLI command with your task description, working directory path, and maximum iteration count. Specify the task, set the target directory, and define iteration limits to control the collaborative workflow execution scope.

Yes, you can select between Copilot and Codex runtimes for team workflow orchestration by passing the runtime flag or setting the OMC_RUNTIME environment variable. This allows deterministic execution through your preferred runtime environment.

Yes, team orchestration supports multi-person feature task coordination by guiding iterative development cycles and ensuring all required reviews are completed before test runs execute. It coordinates collaborative scenarios across multiple iterations.

Tests are not running because the review-first verification mechanism requires clean review outcomes before allowing test execution. The workflow gates test runs behind completed reviews to prevent faulty or unreviewed changes from progressing.