createorg

If $ARGUMENTS is empty: Output the following and wait.

---

MASTERMIND: CREATE ORG

An org is a named, persistent agent team, run by the Org Runtime daemon — not a one-shot Mastermind run and not a Task-tool-spawned boss. Once created, every role in the config starts as its own live agent session the moment you run the org; roles message each other directly (no shared task board) and the org keeps running until stopped.

Use orgs when the work is ongoing, or when independent parts must beat a deadline. Small or sequential one-off work is better served by a single agent session: mastermind-createorg picks the structure from the measured results and says so when an org is not warranted. The skill owns that guidance; this command only parses options and dispatches to it.

What you provide:

• A goal — what should this org continuously accomplish?
• Optional roles — or let Mastermind suggest them from the goal

Examples:

/mastermind:createorg A content team that publishes 3 blog posts per week — writer, editor, SEO reviewer, publisher

/mastermind:createorg --name research-pod Weekly competitor intelligence: researcher, analyst, summarizer

/mastermind:createorg --auto An engineering team for ongoing feature development on my SaaS product

Options: --name <slug> — org identifier used with monomind org run <name> (derived from goal if omitted) --roles <list> — explicit role list (e.g. "boss, writer, reviewer, marketer") --schedule <interval> — daemon schedule for monomind org serve to pick up, e.g. "30m", "2h", "1440m" for daily (omit for a manual, one-shot org) --max-run <interval> — wall-clock bound on ONE scheduled cycle, same format (e.g. "90m"). Defaults to the schedule interval. A cycle hitting this bound is force-stopped with a 60s drain, so size it to how long the work takes, not how often you want it run. --auto — skip confirmation, create immediately --confirm — always ask before saving (default) --delete <name> — delete a saved org and all associated data files (monomind org delete <name> --yes) --list — list all saved orgs with their status (monomind org list)

Once created, start the org with monomind org run <name> (foreground, one-shot) or let monomind org serve pick it up if --schedule was set. Check status with monomind org status <name>; stop with monomind org stop <name>.

---

If $ARGUMENTS is non-empty: Execute the flow below.

---

Parse $ARGUMENTS for:

• --auto flag → mode = auto (no confirmation prompt)
• --confirm flag → mode = confirm
• --name <name> → org_name = (must match ^[a-z0-9][a-z0-9-]{0,63}$; if omitted, derived from goal)
• --roles <desc> → roles_desc = (explicit role list, e.g. "boss, writer, reviewer, marketer")
• --max-run <interval> → max_run = , same daemon format as --schedule
• --schedule <interval> → schedule = , daemon format only: "<N>s", "<N>m", or "<N>h" (e.g. "30m", "2h") — this is passed straight into parseSchedule() in orgrt/scheduler.ts, whose regex ^(\d+)\s*(s|m|h)$ rejects anything else (e.g. "every 30 minutes", "daily") and silently leaves the org unscheduled
• --delete <name> → delete_mode = true, delete_name =
• --list flag → list_mode = true
• Remaining text = prompt (goal description)

If --list flag is set:

# org list knows how to skip artifact side-car files (-state/-goals/…) and
# shows role count, schedule, and runtime status per org
npx -y monomind@latest org list || {
  # fallback for environments without the CLI: config files only
  orgs_dir=".monomind/orgs"
  if [ ! -d "$orgs_dir" ] || [ -z "$(ls "$orgs_dir"/*.json 2>/dev/null)" ]; then
    echo "No saved orgs. Run /mastermind:createorg <goal> to create one."
  else
    echo "Saved orgs:"
    ls "$orgs_dir"/*.json | grep -vE -- '-(state|goals|threads|activity|approvals|members|secrets|budgets|routines|issues|projects|workspaces|worktrees|environments|plugins|adapters|join-requests|bootstrap|project-workspaces|approval-comments|skills)\.json$' \
      | while IFS= read -r f; do
          echo "  • $(basename "$f" .json) — $(jq -r '.goal // ""' "$f" 2>/dev/null | cut -c1-60)"
        done
  fi
}

Stop after listing. Do not proceed to skill invocation.