cancel

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

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill cancel-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/cancel
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill cancel-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cancel and clean up any active OMC mode to ensure a clean, restartable state.

Core Features & Use Cases

  • Graceful cancellation that detects the active mode and terminates it safely.
  • Dependency-aware cleanup across related modes (Autopilot, Ralph, Ultrawork, UltraQA, Swarm, Ultrapilot, Pipeline, Team).
  • Forceful cleanup option to erase remaining legacy state and artifacts when necessary.

Quick Start

Invoke the cancel skill for the current session to safely terminate all active OMC modes and clean up resources.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I safely cancel active workflow orchestration modes and clean up their state?

To safely cancel active workflow orchestration modes, invoke a cancellation process that detects running sessions and terminates them gracefully. It follows dependency order across modes like autopilot, ralph, and ultrawork to ensure clean, restartable state management.

What is the dependency order for cleaning up multiple active OMC sessions?

The dependency order for cleaning up active OMC sessions is autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, and team. This sequence ensures that related workflow orchestration modes are terminated safely without leaving residual state management artifacts.

Can I forcefully clear all legacy state and artifacts from canceled workflow sessions?

Yes, you can forcefully clear all legacy state and artifacts from canceled workflow sessions by using the --force or --all option. This erases remaining session data across all active modes, ensuring a completely clean environment for state management restart.

Does canceling workflow modes preserve Autopilot resume data for future sessions?

Canceling workflow modes preserves Autopilot resume data where applicable during the cleanup process. The session-aware state management tools detect active modes and perform per-session cleanup, ensuring graceful cancellation maintains critical restart information.

When should I use a forceful cleanup instead of a graceful workflow cancellation?

You should use a forceful cleanup instead of graceful workflow cancellation when legacy state and artifacts remain after standard termination. If normal session-aware cleanup fails to achieve a clean, restartable state, the --force option clears all residual data.