cancel

Stop active OMD execution modes and clean related state files.

28|5|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/MeroZemory/oh-my-droid --skill cancel-merozemory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/MeroZemory/oh-my-droid/tree/main/skills/cancel
Command: npx skills add https://github.com/MeroZemory/oh-my-droid --skill cancel-merozemory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents runaway OMD orchestrations by detecting and terminating any active autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, or plan consensus mode while preserving relevant state when needed.

Core Features & Use Cases

  • Automatic Mode Detection: Inspects .omd/state files (JSON and SQLite) to identify the active execution mode.
  • Dependency-aware Cleanup: Cancelling autopilot also tears down linked ralph, ultrawork, ecomode, and ultraqa instances before marking autopilot inactive for a clean resume.
  • Force Clear All: --force or --all wipes every supported state artifact so you can restart from scratch.
  • Use Case: When a long-running Factory Droid autopilot run stalls or misbehaves, run this skill to gracefully halt execution without corrupting saved progress.

Quick Start

Invoke the cancel skill by running /cancel to stop the current OMD mode immediately.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I stop a running Factory Droid autopilot mode without losing saved progress?

To stop a running Factory Droid autopilot mode gracefully, run /cancel to halt execution while preserving relevant state files. It performs dependency-aware cleanup, tearing down linked ralph, ultrawork, ecomode, and ultraqa instances before marking autopilot inactive.

What happens when I cancel OMD swarm or ultrapilot workflows?

Canceling OMD swarm or ultrapilot workflows stops all active execution modes and removes linked state artifacts. The system inspects .omd/state JSON and SQLite files to detect the active mode and ensures dependency-aware cleanups for a clean resume.

Can I force a full state purge across all active OMD execution modes?

Yes, you can force a full state purge across all active OMD execution modes by running /cancel with the --force or --all flag. This wipes every supported state artifact, allowing you to restart Factory Droid orchestrations from scratch.

Does the cancel command support tearing down linked dependencies like ralph and ultraqa?

Yes, the cancel command supports dependency-aware teardown by checking state files and removing linked mode artifacts. Canceling autopilot automatically terminates associated ralph, ultrawork, ecomode, and ultraqa instances to prevent orphaned processes.

Why does my OMD orchestrator leave behind state files after stopping a pipeline run?

OMD orchestrators leave behind state files after stopping a pipeline run to preserve progress for a clean resume. The cancel skill performs dependency-aware cleanup by default, or you can use the --force flag to completely wipe all state artifacts.

When should I use a forced state cleanup instead of a graceful OMD cancellation?

Use a forced state cleanup with --force or --all instead of a graceful OMD cancellation when a long-running autopilot run stalls or misbehaves and you need to restart from scratch, wiping every supported state artifact to prevent corruption.