Fetches cancel from yeachan-heo/oh-my-claudecode and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/cancel
Restart Cursor to activate cancel. Access via /cancel in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Intelligent cancellation that detects and cancels the active OMC mode.
The cancel skill is the standard way to complete and exit any OMC mode.
When the stop hook detects work is complete, it instructs the LLM to invoke
this skill for proper state cleanup. If cancel fails or is interrupted,
retry with --force flag, or wait for the 2-hour staleness timeout as
a last resort.
What It Does
Automatically detects which mode is active and cancels it:
Autopilot: Stops workflow, preserves progress for resume
Ralph: Stops persistence loop, clears linked ultrawork if applicable
Ultrawork: Stops parallel execution (standalone or linked)
Team: Sends shutdown_request to all teammates, waits for responses, calls TeamDelete, clears linked ralph if present
Team+Ralph (linked): Cancels team first (graceful shutdown), then clears ralph state. Cancelling ralph when linked also cancels team first.
Usage
/oh-my-claudecode:cancel
Or say: "cancelomc", "stopomc"
Critical: Deferred Tool Handling
The state management tools (state_clear, state_read, state_write, state_list_active,
state_get_status) may be registered as deferred tools by Claude Code. Before calling
any state tool, you MUST first load all of them via ToolSearch:
If state_clear is unavailable or fails, use this bash fallback as an emergency
escape from the stop hook loop. This is NOT a full replacement for the cancel flow —
it only removes state files to unblock the session. Linked modes (e.g. ralph→ultrawork,
autopilot→ralph/ultraqa) must be cleared separately by running the fallback once per mode.
Replace MODE with the specific mode (e.g. ralplan, ralph, ultrawork, ultraqa).
WARNING: Do NOT use this fallback for autopilot or omc-teams. Autopilot requires
state_write(active=false) to preserve resume data. omc-teams requires tmux session
cleanup that cannot be done via file deletion alone.
# Fallback: direct file removal when state_clear MCP tool is unavailableSESSION_ID="${CLAUDE_SESSION_ID:-${CLAUDECODE_SESSION_ID:-}}"REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || { d="$PWD"; while [ "$d" != "/" ] && [ ! -d "$d/.omc" ]; do d="$(dirname"$d")";done;echo"$d";})"
# Cross-platform SHA-256 (macOS: shasum, Linux: sha256sum)
sha256portable() { printf '%s' "$1" | (sha256sum 2>/dev/null || shasum -a 256) | cut -c1-16; }
# Resolve state directory (supports OMC_STATE_DIR centralized storage)
if [ -n "${OMC_STATE_DIR:-}" ]; then
# Mirror getProjectIdentifier() from worktree-paths.ts
SOURCE="$(git remote get-url origin 2>/dev/null ||echo"$REPO_ROOT")"
HASH="$(sha256portable "$SOURCE")"
DIR_NAME="$(basename"$REPO_ROOT"|sed's/[^a-zA-Z0-9_-]/_/g')"
OMC_STATE="$OMC_STATE_DIR/${DIR_NAME}-${HASH}/state"
[ ! -d "$OMC_STATE" ] && { echo "ERROR: State dir not found at $OMC_STATE" >&2; exit 1; }
elif [ "$REPO_ROOT" != "/" ] && [ -d "$REPO_ROOT/.omc" ]; then
OMC_STATE="$REPO_ROOT/.omc/state"
else
echo "ERROR: Could not locate .omc state directory" >&2
exit 1
fi
MODE="ralplan" # <-- replace with the target mode
# Clear session-scoped state for the specific mode
if [ -n "$SESSION_ID" ] && [ -d "$OMC_STATE/sessions/$SESSION_ID" ]; then
rm -f "$OMC_STATE/sessions/$SESSION_ID/${MODE}-state.json"
rm -f "$OMC_STATE/sessions/$SESSION_ID/${MODE}-stop-breaker.json"
# Write cancel signal so stop hook detects cancellation in progress
NOW_ISO="$(date-u +"%Y-%m-%dT%H:%M:%SZ")"
EXPIRES_ISO="$(date-u-d"+30 seconds" +"%Y-%m-%dT%H:%M:%SZ"2>/dev/null || python3 - <<'PY'\nfrom datetime import datetime, timedelta, timezone\nprint((datetime.now(timezone.utc) + timedelta(seconds=30)).strftime('%Y-%m-%dT%H:%M:%SZ'))\nPY\n)"
printf '{"active":true,"requested_at":"%s","expires_at":"%s","mode":"%s","source":"bash_fallback"}' \
"$NOW_ISO" "$EXPIRES_ISO" "$MODE" > "$OMC_STATE/sessions/$SESSION_ID/cancel-signal-state.json"
fi
# Clear legacy state only if no session ID (avoid clearing another session's state)
if [ -z "$SESSION_ID" ]; then
rm -f "$OMC_STATE/${MODE}-state.json"
fi
Auto-Detection
/oh-my-claudecode:cancel follows the session-aware state contract:
By default the command inspects the current session via state_list_active and state_get_status, navigating .omc/state/sessions/{sessionId}/… to discover which mode is active.
When a session id is provided or already known, that session-scoped path is authoritative. Legacy files in .omc/state/*.json are consulted only as a compatibility fallback if the session id is missing or empty.
Swarm is a shared SQLite/marker mode (.omc/state/swarm.db / .omc/state/swarm-active.marker) and is not session-scoped.
The default cleanup flow calls state_clear with the session id to remove only the matching session files; modes stay bound to their originating session.
Active modes are still cancelled in dependency order:
Self-Improve (standalone — clear state, clean orphaned worktrees, preserve iteration_state for resume, set status: "user_stopped" in .omc/self-improve/state/agent-settings.json)
Force Clear All
Use --force or --all when you need to erase every session plus legacy artifacts, e.g., to reset the workspace entirely.
/oh-my-claudecode:cancel --force
/oh-my-claudecode:cancel --all
Steps under the hood:
state_list_active enumerates .omc/state/sessions/{sessionId}/… to find every known session.
state_clear runs once per session to drop that session’s files.
A global state_clear without session_id removes legacy files under .omc/state/*.json, .omc/state/swarm*.db, and compatibility artifacts (see list).
Team artifacts (~/.claude/teams/*/, ~/.claude/tasks/*/, .omc/state/team-state.json) are best-effort cleared as part of the legacy fallback.
Cancel for native team does NOT affect omc-teams state, and vice versa.
Every state_clear command honors the session_id argument, so even force mode still uses the session-aware paths first before deleting legacy files.
Legacy compatibility list (removed only under --force/--all):
.omc/state/autopilot-state.json
.omc/state/ralph-state.json
.omc/state/ralph-plan-state.json
.omc/state/ralph-verification.json
.omc/state/ultrawork-state.json
.omc/state/ultraqa-state.json
.omc/state/swarm.db
.omc/state/swarm.db-wal
.omc/state/swarm.db-shm
.omc/state/swarm-active.marker
.omc/state/swarm-tasks.db
.omc/state/ultrapilot-state.json
.omc/state/ultrapilot-ownership.json
.omc/state/pipeline-state.json
.omc/state/omc-teams-state.json
.omc/state/plan-consensus.json
.omc/state/ralplan-state.json
.omc/state/boulder.json
.omc/state/hud-state.json
.omc/state/subagent-tracking.json
.omc/state/subagent-tracker.lock
.omc/state/rate-limit-daemon.pid
.omc/state/rate-limit-daemon.log
.omc/state/checkpoints/ (directory)
.omc/state/sessions/ (empty directory cleanup after clearing sessions)
Implementation Steps
When you invoke this skill:
1. Parse Arguments
# Check for --force or --all flagsFORCE_MODE=false
if[["$*"== *"--force"* ]]||[["$*"== *"--all"* ]];thenFORCE_MODE=true
fi
2. Detect Active Modes
The skill now relies on the session-aware state contract rather than hard-coded file paths:
Call state_list_active to enumerate .omc/state/sessions/{sessionId}/… and discover every active session.
For each session id, call state_get_status to learn which mode is running (autopilot, ralph, ultrawork, etc.) and whether dependent modes exist.
If a session_id was supplied to /oh-my-claudecode:cancel, skip legacy fallback entirely and operate solely within that session path; otherwise, consult legacy files in .omc/state/*.json only if the state tools report no active session. Swarm remains a shared SQLite/marker mode outside session scoping.
Any cancellation logic in this doc mirrors the dependency order discovered via state tools (autopilot → ralph → …).
3A. Force Mode (if --force or --all)
Use force mode to clear every session plus legacy artifacts via state_clear. Direct file removal is reserved for legacy cleanup when the state tools report no active sessions.
3B. Smart Cancellation (default)
If Team Active (Claude Code native)
Teams are detected by checking for config files in ~/.claude/teams/:
# Check for active teamsTEAM_CONFIGS=$(find ~/.claude/teams -name config.json -maxdepth22>/dev/null)
Two-pass cancellation protocol:
Pass 1: Graceful Shutdown
For each team found in ~/.claude/teams/:
1. Read config.json to get team_name and members list
2. For each non-lead member:
a. Send shutdown_request via SendMessage
b. Wait up to 15 seconds for shutdown_response
c. If response received: member terminates and is auto-removed
d. If timeout: mark member as unresponsive, continue to next
3. Log: "Graceful pass: X/Y members responded"
Pass 2: Reconciliation
After graceful pass:
1. Re-read config.json to check remaining members
2. If only lead remains (or config is empty): proceed to TeamDelete
3. If unresponsive members remain:
a. Wait 5 more seconds (they may still be processing)
b. Re-read config.json again
c. If still stuck: attempt TeamDelete anyway
d. If TeamDelete fails: report manual cleanup path
TeamDelete + Cleanup:
1. Call TeamDelete() — removes ~/.claude/teams/{name}/ and ~/.claude/tasks/{name}/
2. Clear team state: state_clear(mode="team")
3. Check for linked ralph: state_read(mode="ralph") — if linked_team is true:
a. Clear ralph state: state_clear(mode="ralph")
b. Clear linked ultrawork if present: state_clear(mode="ultrawork")
4. Run orphan scan (see below)
5. Emit structured cancel report
Orphan Detection (Post-Cleanup):
After TeamDelete, verify no agent processes remain:
node
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
