Menü
Abort the current WorkBuddy workflow — stop background agents/processes, clear in-progress tasks, and hand back control to the user
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | cancel |
| category | utility |
| status | active |
| description | Abort the current WorkBuddy workflow — stop background agents/processes, clear in-progress tasks, and hand back control to the user |
| agent_created | true |
| triggers | ["cancel","stop","abort","cancel this","stop the task"] |
Ported from oh-my-codex
cancel. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
The standard, safe way to stop whatever is currently running and exit cleanly.
WorkBuddy has no persistent "mode" state like OMX's .omx/state/*.json, so there is
nothing to terminalize across sessions — but in-progress work within the current session
can still be stopped. Use this skill whenever the user says "cancel", "stop", "abort", or
asks to halt the current flow.
run_in_background)
is running, stop it with the TaskStop tool (or send its task_id).in_progress task as completed only if it is genuinely
done; otherwise set it back to pending so it is not silently lost, or delete it. Do not leave
phantom in_progress items..workbuddy/memory/YYYY-MM-DD.md. Do not delete user files./cancel
Or say: "cancel", "stop", "abort".
WorkBuddy sessions are stateless between turns, so a simple "stop" already resets the flow.
Use --force / --all semantics only to also:
.workbuddy/memory scratch notes you created for this run if the user wants a clean slate.Example:
/cancel --force
Run a regression-tests-first, smell-by-smell deslop/refactor workflow that preserves behavior and raises signal quality. Use when the user asks to "cleanup", "refactor", "deslop", or when follow-up code has duplicates, dead code, weak boundaries, or fallback-like slop.
Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says "analyze", "investigate", "why does", "what's causing", or needs grounded cross-file explanation before any changes are proposed.
Deprecated compatibility shim for Claude advisor requests. Use `ask` with the claude backend instead.
Deprecated compatibility shim for Gemini advisor requests. Use `ask` with the gemini backend instead.
Ask a locally installed external advisor CLI (Claude or Gemini) for focused questions, reviews, brainstorming, or second opinions, and capture a reusable artifact. Use when the user wants a Claude/Gemini second opinion, "ask claude", or "ask gemini".
Strict autonomous delivery loop that runs deep-interview, ralplan, ultragoal, code-review, and ultraqa in order with automatic re-planning when gates are not clean. Use on "autopilot", "autonomous", "build me", "create me", "make me", "full auto", "handle it all", or "I want a/an…".