cancel

Cancel active Omagy workflows via Antigravity CLI commands.

3|Updated May 24, 2026
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill cancel-shayne-snap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/cancel
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill cancel-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you halt an active Omagy workflow when you want to cancel, abort, or clear its current execution state without manually editing internal files.

Core Features & Use Cases

  • Workflow cancellation via CLI: Stops the active Omagy workflow through the Antigravity runtime.
  • Mode-targeted cancellation: Lets you cancel a specific workflow type (ultrawork, ralph, or team) when multiple modes may be running.
  • Full-state cancellation: Clears all Omagy workflow state when you explicitly request stopping everything.

Use case: You started an execution path (like team or ralph), realize the plan was wrong, and want to immediately stop the current run so you can re-plan or switch direction.

Quick Start

Ask to cancel the current Omagy workflow by saying: omagy 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 Omagy workflow safely without editing internal state files?

The omagy cancel command halts the active Omagy workflow via the Antigravity runtime without requiring manual edits to internal state files.

What is the best way to cancel a specific workflow mode like ultrawork or ralph when multiple are running?

Mode-targeted cancellation disambiguates the active run and stops only the requested workflow type, such as ultrawork, ralph, or team.

Can I clear all Omagy workflow state at once?

Yes, explicitly requesting a full-state cancellation stops every active execution path and clears the entire Omagy workflow state.

Does workflow cancellation support lifecycle hooks and report canonical outcomes?

Yes, workflow cancellation supports lifecycle hooks and reports canonical userinterlude lifecycle outcomes, ensuring the active workflow stops cleanly through the CLI without direct state edits.

When should I use a CLI workflow cancel command instead of manually managing state?

Use the CLI cancel command when a workflow plan is wrong and you need to immediately stop the current run to re-plan or switch direction, avoiding risky direct state edits.