mastermind stoporg command (monomind)
Scanned 9/10/2026
Install to Claude Code
npx -y skills add monoes/monomind --skill monomind-monomind-mastermind-stoporg --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Monomind Monomind Mastermind Stoporg?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/monoes-monomind-monomind-mastermind-stoporg)More formats (shields.io, HTML) on the badges page.
---
description: mastermind stoporg command (monomind)
type: flow
name: monomind-monomind-mastermind-stoporg
---
<!-- Stop a running scheduled org loop. Sets status to "stopped" — the next scheduled wakeup reads the status, skips all work, and does not reschedule. Loop dies within one interval. -->
**If $ARGUMENTS is empty:** Output the following and wait.
---
**MASTERMIND: STOP ORG**
Stops a scheduled org loop cleanly. The org's `status` is set to `"stopped"` — the next scheduled wakeup will read the status, skip all work, and not reschedule itself. The loop is guaranteed to die within one interval (no orphaned wakeups).
**Usage:**
```
/mastermind:stoporg --org <name>
```
**Examples:**
```
/mastermind:stoporg --org livarto-issue-resolver
/mastermind:stoporg --org research-pod
```
**Lifecycle:**
```
stopped → (runorg) → active
active → (stoporg) → stopped
active → (HIL) → paused (set manually in .monomind/orgs/<name>.json)
paused → (set active) → active (resume by setting status back to "active" in the JSON)
```
**Note:** v2 orgs (the default) are stopped via `monomind org stop <name>` — this
command handles both: it routes v2 orgs to the CLI and legacy `.loop` orgs
through the v1 status-flip path.
Your orgs (with live runtime status):
```bash
npx -y monomind@latest org list 2>/dev/null || echo "(none — run /mastermind:createorg to define one)"
```
---
**If $ARGUMENTS is non-empty:** Execute the flow below.
---
Parse `$ARGUMENTS` for:
- `--org <name>` → org_name = <name>
If `--org` is not provided, list orgs with schedules and ask which to stop.
Verify the org file exists:
```bash
[ -f ".monomind/orgs/${org_name}.json" ] || { echo "Org '${org_name}' not found."; exit 1; }
```
Generate a session ID:
```bash
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
session_id="mm-$(date -u +%Y%m%dT%H%M%S)"
CTRL_URL=$(jq -r '.url // "http://localhost:4242"' "$REPO_ROOT/.monomind/control.json" 2>/dev/null || echo "http://localhost:4242")
```
Invoke `Skill("mastermind-stoporg")` passing: org_name: `$org_name`, session_id: `$session_id`, caller: "command".
After skill returns: emit `session:complete`:
```bash
curl -s -X POST "${CTRL_URL}/api/mastermind/event" -H "x-monomind-token: $(cat "${REPO_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}/.monomind/dashboard-token" 2>/dev/null || true)" \
-H "Content-Type: application/json" \
-d "$(jq -cn \
--arg session "$session_id" \
'{type:"session:complete",session:$session,domain:"ops",status:"complete",domains:["ops"],ts:(now*1000|floor)}')" || true
```
Follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.
Invoke `Skill("mastermind-repeat")` now to execute the REPEAT POSTAMBLE. This is a required tool call — do not skip it.

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!