What problem does it solve?
Canceling an active autonomous workflow can leave sessions stuck, state files inconsistent, or linked modes (like persistence loops and QA workers) still running. This Skill resolves that by detecting the currently active OMC mode(s) and stopping the right components in the correct dependency order while preserving any required resume state.
Core Features & Use Cases
- Autodetects active OMC mode(s) across session-scoped workflows (autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team, plan consensus).
- Dependency- and link-aware cancellation ensures correct teardown ordering (e.g., autopilot cascades to linked ralph/ultraqa cleanup; ralph cascades to linked ultrawork).
- Force/global cleanup support clears all sessions plus legacy artifacts when you truly need a full reset.
- Team graceful shutdown for Claude Code teams signals teammates, waits for shutdown responses, then performs registry and state cleanup with an orphan-process scan.
- Emergency fallback provides a last-resort state-file cleanup path when state tools are unavailable (with explicit guardrails for modes that require special handling).
Quick Start
Use the cancel command to stop the currently running OMC mode: set off the flow with /oh-my-claudecode:cancel.