workflow-orchestrator

To generate a workflow orchestration plan, the orchestrator reads a repository diagnostic sensemaking brief, selects the appropriate workflow from the registry, and stages the ordered execution steps based on your specified plan_only mode. This maps diagnostics directly to safe execution pipelines.

Approval gates enforce safe workflow execution by requiring explicit user authorization before proceeding through sensitive registry steps. The orchestrator applies these gates during mode-aware orchestration to prevent unauthorized actions and cascading failures.

When an artifact contract is missing or invalid, the orchestrator triggers a hard-stop condition to prevent drift. Artifact-contract enforcement ensures every step's handoff complies with required schemas before allowing the workflow to continue.

Yes, you can execute workflows using YOLO mode, but it requires explicit opt-in due to safety rules. YOLO execution bypasses standard approval gates to run steps rapidly, relying on strict execution authority constraints to prevent forbidden actions.

Execution authority constraints limit the orchestrator to executing only registry-approved steps available locally. It enforces strict restrictions on external and prompt-only steps, triggering hard-stops if forbidden step types are detected in the workflow.

You should use plan_only mode when you need to generate a workflow orchestration plan or prompt chain without executing actions. It allows you to review the staged repository steps and artifact contracts before committing to full gated execution.