cancel

To stop a runaway OMC workflow, use the cancel skill to safely exit the active mode and clean up its state. It detects the running mode, invokes state tools to clear session artifacts, and performs correct dependency-aware shutdown.

The safest way to cancel active agent orchestration modes is using the cancel skill. It handles linked-mode dependencies by cascading cancellations in the correct order and clears the associated session state to prevent stuck workflows.

To gracefully shutdown a team workflow, the cancel skill sends shutdown requests to teammates, reconciles remaining members, and performs team deletion followed by orphan cleanup. This ensures all linked agents are properly deactivated.

If normal workflow cancellation is interrupted, the cancel skill applies a force clear using --force or --all flags to erase session and legacy artifacts. An emergency bash fallback is available to ensure state cleanup completes.

Yes, the cancel skill supports all OMC modes including ultrawork, ultraqa, pipeline, ralph, ultrapilot, autopilot, and swarm. It automatically detects the active mode and applies the appropriate state cleanup and dependency handling.