cancel

Cancel active OMC modes with dependency-aware teardown and state cleanup.

Updated Apr 29, 2026

Search Tags:#state management #orchestration #cancellation #omc #team shutdown #dependency cleanup

Ready to run

npx skills add https://github.com/nichobbs/lyric-lang --skill cancel-nichobbs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/nichobbs/lyric-lang/tree/main/.claude/skills/cancel
Command: npx skills add https://github.com/nichobbs/lyric-lang --skill cancel-nichobbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancels and cleans up any currently running OMC mode so you can regain control without leaving stale orchestration state behind.

Core Features & Use Cases

Auto-detect active mode: Identifies which of these modes are running and cancels them accordingly (autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team).
Dependency-aware cancellation: Cancels linked modes in the correct order (e.g., autopilot cascades to ralph/ultraqa; ralph cascades to linked ultrawork).
Session-safe state cleanup with fallbacks: Uses session-scoped state tools when available and provides an emergency bash fallback when state tools are unavailable, with explicit warnings for autopilot and omc-teams.
Graceful native Team shutdown: Sends shutdown requests, waits for responses, reconciles remaining members, and then performs TeamDelete plus orphan checks.

Quick Start

Use cancel to stop whatever OMC mode is currently active by running: /oh-my-claudecode:cancel

Frequently Asked Questions about cancel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I stop an active OMC orchestration mode and clean up its state?▼

To stop an active OMC orchestration mode, run the cancel command to auto-detect the running mode, tear down linked dependencies in correct order, and issue a final state clear to prevent stop-hook reinforcements.

What is the safest way to cancel a running autopilot or team workflow?▼

Canceling a running autopilot or team workflow safely requires dependency-aware teardown that cascades cancellation to linked modes like ralph or ultraqa, followed by native team shutdown requests and orphan reconciliation checks.

Why does stale orchestration state persist after stopping an OMC mode?▼

Stale orchestration state persists when a stop does not issue a final state clear for skill-active, which prevents stop-hook reinforcements from re-triggering; session-scoped state tools and dependency-ordered cleanup resolve this.

Can I force stop an OMC mode across multiple sessions when state tools are unavailable?▼

Yes, you can force stop an OMC mode across sessions using an emergency bash fallback that clears state when session-scoped state tools are unavailable, though this triggers explicit warnings for autopilot and omc-teams.

How do linked OMC modes cascade during a cancellation?▼

Linked OMC modes cascade during cancellation by honoring dependency order, meaning autopilot cancellation triggers ralph and ultraqa teardown, while ralph cancellation cascades to its linked ultrawork mode.

Does OMC team shutdown wait for member responses before deleting the team?▼

Yes, OMC team shutdown sends shutdown requests, waits for member responses, reconciles any remaining members, and then performs a TeamDelete followed by an orphan check to ensure complete cleanup.