cancel

Cancel active OMC modes and clean up related state across sessions.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Pryma-Tech/iris --skill cancel-pryma-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Pryma-Tech/iris/tree/main/cli/skills/cancel
Command: npx skills add https://github.com/Pryma-Tech/iris --skill cancel-pryma-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel any active OMC mode (autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team) and perform proper cleanup to prevent lingering state or undesired restarts.

Core Features & Use Cases

  • Detects the active OMC mode across sessions and cancels it in dependency order (autopilot → ralph → ultrawork → ultraqa → swarm → ultrapilot → pipeline → team), preserving resume data where applicable.
  • Supports forceful, global cleanup with --force/--all to clear all session state and legacy artifacts, including orphaned processes and legacy .omc files.
  • Handles native Claude Code teams and automates safe cleanup of related state across linked modes, with safeguards to prevent partial cleanup.

Quick Start

Run the cancel command with optional flags to gracefully terminate active modes and purge state.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I cancel active OMC modes and clean up session state?

To cancel active OMC modes and clean up session state, run the cancel command, which detects active modes across sessions and terminates them in dependency order while clearing the skill-active state.

What happens when I force cancel all OMC modes globally?

Forcing a global cancel with --force or --all purges all session state and legacy artifacts, clearing orphaned processes and legacy .omc files to prevent lingering state or undesired restarts.

In what dependency order are OMC modes terminated during state cleanup?

OMC modes are canceled in dependency order: autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, and team, preserving resume data where applicable during the state cleanup process.

Can I use this to clean up state for native Claude Code teams?

Yes, the cancellation process handles native Claude Code teams and automates safe cleanup of related state across linked modes, deploying safeguards to prevent partial cleanup.

Why does an OMC mode leave lingering state after a session ends?

Lingering state occurs when active OMC modes are not gracefully stopped, which this cancellation process resolves by integrating with Iris state tools to locate active modes and ensure skill-active state is fully cleared.

Do I need Iris state tools to perform an OMC mode cancellation?

No external setup is needed by the user; the cancellation process directly integrates with Iris state tools like state_list_active, state_get_status, and state_clear internally to locate and clear active modes.