Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/goal:stopThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Stop Goal Confirm that the goal has been stopped and that the state file remains available for inspection or later resume.
"${CLAUDE_PLUGIN_ROOT}/bin/goalctl.py" stop
Confirm that the goal has been stopped and that the state file remains available for inspection or later resume.
npx claudepluginhub chrischabot/claude-code-goal --plugin goal/stopToggles pause/resume of the current vibe session. Updates session and status JSON files, invokes explainer, and outputs structured confirmation with progress details.
/stopStops the heartbeat daemon by running `bun run ${CLAUDE_PLUGIN_ROOT}/src/index.ts --stop` and reports the output to the user.
/stopStops the Claude Nights Watch daemon gracefully with SIGTERM, timeouts to SIGKILL if needed, and cleans up PID files and locks. Halts autonomous task execution monitoring.
/stopStops running sparkrun inference workloads by recipe name, cluster ID, or all containers on a cluster. Prompts for target if unspecified and confirms with status.
/stopGracefully stops active OMA autonomous workflow, summarizes completed work, open tasks, blockers, and generates structured recovery plan with checkpoint update.
/stopTerminates an active Hypo-Workflow pipeline, cleaning up resources and aborting in-progress tasks.