What problem does it solve? When running OMX workflow modes like autopilot, ralph, ultrawork, or team, stale state files and orphaned tmux sessions can linger after work completes. This Skill provides a single, safe way to detect which mode is active and shut it down cleanly, preserving resumable progress where supported. ## Core Features & Use Cases - Auto-Detection of Active Modes: Inspects session-scoped state via state_list_active and state_get_status to identify which of the ten OMX modes (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team, plan consensus) is running. - Dependency-Ordered Cancellation: Cancels modes in a defined order, cleaning up linked modes (e.g., ralph's linked ultrawork) while leaving unrelated sessions untouched. - Graceful Team Shutdown: Sends shutdown inboxes to tmux-based team workers, waits for graceful exit, then force-kills unresponsive panes and destroys the tmux session. - Force Reset: The --force or --all flag clears every session plus legacy state files under .omx/state/ for a full workspace reset. - Use Case: After an autopilot run finishes, invoke the cancel skill to mark it inactive while preserving phase, plan, and verdict state so you can resume later with /autopilot. ## Quick Start Ask the AI to cancel the currently active OMX mode, or add the force flag to clear all sessions and legacy state files.