@monoes/monomindcli 2.16.3 → 2.16.5

package/.claude/commands/workflows/workflow-create.md

@@ -1,11 +1,11 @@
 ---
 name: workflows:workflow-create
-description: Create and save custom workflow templates using npx monomind workflow template create — save successful workflows for reuse
+description: Create a reusable multi-agent workflow as an org config with npx monomind org create, then edit and validate it
 ---
 
 # Workflow Create
 
-Create and save custom workflow templates for reuse.
+Create a reusable workflow. The CLI has no `workflow` command; a reusable workflow is an org config in `.monomind/orgs/<name>.json`.
 
 ## How to Invoke
 
@@ -18,66 +18,64 @@ Skill("workflows:workflow-create")
 ## CLI Reference
 
 ```bash
-# Create a template from a workflow ID
-npx monomind workflow template create --name "my-api-workflow" --workflow wf-abc123
+# Scaffold from a starter template
+npx monomind org create api-dev --template dev-team --goal "Deliver API features from the backlog"
 
-# Create a template from a workflow file
-npx monomind workflow template create --name "deploy-workflow" --file ./workflow.yaml
+# Scheduled workflow (hosted by `org serve`)
+npx monomind org create weekly-brief --template research-pod --goal "Weekly AI tooling brief" --schedule 2h
 
-# List existing templates
-npx monomind workflow template list
+# Overwrite an existing config
+npx monomind org create api-dev --template dev-team --force
 
-# Show a specific template's stages and agents
-npx monomind workflow template show development
-```
-
-## Template Create Flags
-
-| Flag | Short | Description |
-|------|-------|-------------|
-| `--name` | `-n` | Template name (required) |
-| `--workflow` | `-w` | Workflow ID to save as template |
-| `--file` | `-f` | Workflow file to save as template |
+# Validate after editing the JSON
+npx monomind org validate api-dev
 
-## MCP Tools
-
-```javascript
-// Create a workflow definition
-mcp__monomind__workflow_create({
-  name: "my-workflow",
-  template: "development",
-  task: "Build auth system"
-})
+# List orgs in the project
+npx monomind org list
+```
 
-// List available templates
-mcp__monomind__workflow_template({})
+## `org create` Flags
 
-// Execute workflow from template
-mcp__monomind__workflow_run({
-  template: "my-workflow",
-  task: "Build feature X"
-})
-```
+| Flag | Description |
+|------|-------------|
+| `--template` | `content-team` \| `dev-team` \| `research-pod` \| `kg-extraction` \| `advisor-orchestrator` |
+| `--goal` | Org goal (defaults to the template's placeholder) |
+| `--schedule` | Daemon schedule, e.g. `30m` or `2h` |
+| `--force` | Overwrite an existing org config |
+| `-y, --yes` | Skip the per-role model confirmation prompt |
 
 ## Workflow
 
-1. Run a workflow that works well:
+1. Scaffold from the closest template:
    ```bash
-   npx monomind workflow run -t development --task "Build auth"
-   # Note the workflowId in the output
+   npx monomind org create auth-flow --template dev-team --goal "Build auth features"
    ```
 
-2. Save it as a reusable template:
+2. Edit `.monomind/orgs/auth-flow.json` — adjust roles, responsibilities, and models. For a guided design, use the `mastermind-createorg` skill; to add a role, use `mastermind-new-agent`.
+
+3. Validate and preview:
    ```bash
-   npx monomind workflow template create --name "auth-workflow" --workflow <workflowId>
+   npx monomind org validate auth-flow
+   npx monomind org run auth-flow --dry-run
    ```
 
-3. Reuse it:
+4. Reuse it:
    ```bash
-   npx monomind workflow run -t auth-workflow --task "New auth task"
+   npx monomind org run auth-flow --task "Add password reset"
    ```
 
+## In-Conversation Alternative
+
+For a one-off workflow, no config is needed: write the stages as a TodoWrite list and spawn Task-tool agents per stage (see `workflows:workflow-execute`). To keep the pattern for later:
+
+```bash
+npx monomind memory store --key "workflow-auth" \
+  --value "plan (planner) -> implement+test in parallel (coder, tester) -> review (reviewer)" \
+  --namespace patterns
+```
+
 ## Related Skills
 
-- `workflows:workflow-execute` — Run workflows from templates
-- `workflows:workflow-export` — Browse and manage templates
+- `workflows:workflow-execute` — Run workflows
+- `workflows:workflow-export` — Inspect and export workflows
+- `mastermind-createorg` — Design an org interactively

package/.claude/commands/workflows/workflow-execute.md

@@ -1,11 +1,11 @@
 ---
 name: workflows:workflow-execute
-description: Run multi-agent workflows using built-in templates (development, research, testing, security-audit, etc.) via real npx monomind workflow run CLI
+description: Run multi-agent workflows — in the conversation with Task-tool agents, or as a persistent org with npx monomind org run
 ---
 
 # Workflow Execute
 
-Run multi-agent workflows using built-in templates or custom workflow files.
+Run a multi-stage, multi-agent workflow. The CLI has no `workflow` command; use one of the two real paths below.
 
 ## How to Invoke
 
@@ -15,87 +15,77 @@ Skill("workflows:workflow-execute")
 
 ---
 
-## CLI Reference
+## Path 1: In the Conversation (Task Tool)
+
+Claude Code executes the stages directly:
+
+1. Break the work into stages with TodoWrite (plan → implement → test → review)
+2. Spawn every independent agent for a stage in ONE message via the Task tool
+3. Wait for results, review them, then start the next stage
+
+```javascript
+// Stage: implement + test in parallel
+Task({ subagent_type: "coder",  prompt: "Implement the auth API in src/auth/ per the plan ..." })
+Task({ subagent_type: "tester", prompt: "Write tests for the auth API contract ..." })
+
+// Next stage: review
+Task({ subagent_type: "reviewer", prompt: "Review the diff in src/auth/ ..." })
+```
+
+Optionally record topology and roster, and track the task for routing:
 
 ```bash
-# Run a built-in template
-npx monomind workflow run -t development --task "Build REST API with auth"
-npx monomind workflow run -t research --task "Analyze performance bottlenecks"
-npx monomind workflow run -t testing
-npx monomind workflow run -t security-audit
-
-# Run from a workflow file
-npx monomind workflow run -f ./workflow.yaml
-npx monomind workflow run -f ./workflow.json
-
-# Validate without executing
-npx monomind workflow run -t development --dry-run
+npx monomind monoswarm init --topology hierarchical --max-agents 8
+npx monomind hooks pre-task --description "Build REST API with auth" --task-id api-auth
+# ... stages run ...
+npx monomind hooks post-task --task-id api-auth --success true
 ```
 
-## All Flags
+## Path 2: As an Org (`monomind org`)
 
-| Flag | Short | Default | Description |
-|------|-------|---------|-------------|
-| `--template` | `-t` | — | Built-in template name |
-| `--file` | `-f` | — | Workflow definition file (YAML/JSON) |
-| `--task` | — | — | Task description passed to the workflow |
-| `--parallel` | `-p` | `true` | Enable parallel agent execution |
-| `--max-agents` | `-m` | `5` | Maximum agents to spawn |
-| `--timeout` | — | `30` | Timeout in minutes |
-| `--dry-run` | `-d` | `false` | Validate without executing |
+For repeatable, scheduled, or long-running workflows:
 
-## Built-in Templates
+```bash
+# Create from a starter template (or use an existing .monomind/orgs/<name>.json)
+npx monomind org create api-dev --template dev-team --goal "Build REST API with auth"
 
-| Template | Stages | Agent Types |
-|----------|--------|-------------|
-| `development` | Planning → Implementation → Testing → Review → Integration | coder, tester, reviewer |
-| `research` | Discovery → Analysis → Synthesis → Documentation | researcher, analyst |
-| `testing` | Unit → Integration → E2E → Performance | tester, coder |
-| `security-audit` | Threat Model → Static → Dynamic → Report | security-architect, auditor |
-| `code-review` | Initial → Security → Quality → Feedback | reviewer, auditor, analyst |
-| `refactoring` | Analysis → Planning → Refactor → Validation | architect, coder, reviewer |
-| `custom` | Define your own | configurable |
+# Validate and preview each role's briefing without starting agents
+npx monomind org validate api-dev
+npx monomind org run api-dev --dry-run
 
-## MCP Tools
+# Run (foreground daemon); override the goal for this run
+npx monomind org run api-dev --task "Add refresh-token rotation"
 
-```javascript
-// Run a workflow
-mcp__monomind__workflow_run({
-  template: "development",
-  task: "Build REST API with auth",
-  options: {
-    parallel: true,
-    maxAgents: 6,
-    timeout: 30,
-    dryRun: false
-  }
-})
-
-// Check workflow status after launch
-mcp__monomind__workflow_status({ workflowId: "wf-123" })
-
-// List all workflows
-mcp__monomind__workflow_list({ status: "running", limit: 10 })
-
-// Stop a running workflow
-mcp__monomind__workflow_cancel({ workflowId: "wf-123" })
+# Cap spend
+npx monomind org run api-dev --budget-usd 5
 ```
 
-## After Launch
+### `org run` Flags
 
-Track progress:
+| Flag | Description |
+|------|-------------|
+| `--task` | Override the org goal for this run |
+| `--dry-run` | Validate and print each role's briefing without starting sessions |
+| `--resume` | Resume from the persisted checkpoint instead of starting fresh |
+| `--budget-usd` | Hard-stop if the upfront cost estimate exceeds this value |
+| `-y, --yes` | Skip the cost-estimate confirmation prompt |
 
-```bash
-# Check status by ID (shown after run)
-npx monomind workflow status <workflowId>
+## After Launch
 
-# List all running workflows
-npx monomind workflow list --status running
+```bash
+npx monomind org status api-dev          # runtime state
+npx monomind org logs api-dev --follow   # live event log
+npx monomind org questions api-dev       # pending ask_human questions
+npx monomind org approvals api-dev       # pending tool approvals
+npx monomind org pause api-dev           # finish current turns, start no new cycles
+npx monomind org stop api-dev            # stop the daemon
+npx monomind org report api-dev          # outcome, per-role activity, tokens
 ```
 
 ## Related Skills
 
-- `workflows:workflow-create` — Save a custom workflow template
-- `workflows:development` — Development workflow coordination pattern
-- `workflows:research` — Research workflow coordination pattern
-- `swarm:swarm` — Direct swarm init for custom coordination
+- `workflows:workflow-create` — Create a reusable workflow as an org config
+- `workflows:development` — Development workflow pattern
+- `workflows:research` — Research workflow pattern
+- `monoswarm:monoswarm` — Monoswarm coordination
+- `mastermind-runorg` — Start a saved org

package/.claude/commands/workflows/workflow-export.md

@@ -1,11 +1,11 @@
 ---
 name: workflows:workflow-export
-description: Browse, inspect, and manage workflow templates — list built-in templates, show template details and stages, validate workflow files
+description: Inspect and export workflows — list org configs, export an org's flow as a Mermaid diagram, summarize runs, and print portable Mastermind procedures
 ---
 
-# Workflow Templates
+# Workflow Export
 
-Browse and manage workflow templates — inspect built-in templates and validate custom workflow files.
+Inspect and export workflows. The CLI has no `workflow` command; the real equivalents operate on org configs (`.monomind/orgs/<name>.json`) and Mastermind procedures.
 
 ## How to Invoke
 
@@ -18,71 +18,45 @@ Skill("workflows:workflow-export")
 ## CLI Reference
 
 ```bash
-# List all available templates
-npx monomind workflow template list
-
-# Show details for a specific template (stages, agents, estimated duration)
-npx monomind workflow template show development
-npx monomind workflow template show security-audit
-
-# Validate a custom workflow file
-npx monomind workflow validate -f ./workflow.yaml
-npx monomind workflow validate -f ./workflow.json --strict
-
-# List past workflow runs
-npx monomind workflow list --status completed --limit 20
-npx monomind workflow list --status all
+# List orgs (workflows) in the project and their runtime state
+npx monomind org list
+npx monomind org status
+
+# Validate one or all org configs
+npx monomind org validate api-dev
+npx monomind org validate
+
+# Export an org's flow as a Mermaid diagram (latest run by default)
+npx monomind org flow api-dev
+npx monomind org flow api-dev --run <run-id>
+
+# Summarize runs
+npx monomind org report api-dev
+npx monomind org report api-dev --all
+npx monomind org report api-dev --by-role
+npx monomind org report api-dev --format mermaid
+
+# Portable step-by-step procedures for platforms without native skills
+npx monomind mastermind --list
+npx monomind mastermind run plan --print > plan-workflow.md
 ```
 
-## Built-in Templates Reference
-
-| Template | Stages | Estimated Duration |
-|----------|--------|--------------------|
-| `development` | Planning → Implementation → Testing → Review → Integration | 15-30 min |
-| `research` | Discovery → Analysis → Synthesis → Documentation | 10-20 min |
-| `testing` | Unit → Integration → E2E → Performance | 5-15 min |
-| `security-audit` | Threat Model → Static → Dynamic → Report | 20-40 min |
-| `code-review` | Initial → Security → Quality → Feedback | 10-25 min |
-| `refactoring` | Analysis → Planning → Refactor → Validation | 15-35 min |
-| `custom` | Define your own stages | varies |
-
-## MCP Tools
-
-```javascript
-// List templates
-mcp__monomind__workflow_template({})
+## Sharing a Workflow
 
-// List past workflow runs
-mcp__monomind__workflow_list({ status: "completed", limit: 20 })
+The org config is a plain JSON file, so it can be copied into another project's `.monomind/orgs/` and checked with `npx monomind org validate <name>`. For a full archive with the org's data, use the `mastermind-export` skill (and `mastermind-import` on the other side).
 
-// Get status of a specific run
-mcp__monomind__workflow_status({ workflowId: "wf-123" })
-```
-
-## Workflow File Format
-
-To create a custom workflow file for use with `workflow run -f`:
-
-```yaml
-name: my-workflow
-stages:
-  - name: Planning
-    agents: [architect]
-  - name: Implementation
-    agents: [coder]
-  - name: Testing
-    agents: [tester]
-  - name: Review
-    agents: [reviewer]
-```
+## Org Starter Templates
 
-Validate before running:
-
-```bash
-npx monomind workflow validate -f ./my-workflow.yaml --strict
-```
+| Template | Roles |
+|----------|-------|
+| `dev-team` | tech-lead, developer, code-reviewer, qa |
+| `research-pod` | lead-analyst, researcher, fact-checker |
+| `content-team` | editor-in-chief, writer, reviewer |
+| `kg-extraction` | kg-lead, entity-extractor, relationship-resolver, ontology-validator |
+| `advisor-orchestrator` | advisor, worker-1, worker-2 |
 
 ## Related Skills
 
-- `workflows:workflow-execute` — Run workflows from templates
-- `workflows:workflow-create` — Save a custom workflow as a template
+- `workflows:workflow-execute` — Run workflows
+- `workflows:workflow-create` — Create a reusable workflow
+- `mastermind-export` / `mastermind-import` — Org archives