@monoes/monomindcli 2.16.4 → 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

package/.claude/helpers/build-skill-registry.cjs

@@ -20,8 +20,9 @@
  * Org skill library (`orgSkills`, via org-skill-index.cjs). The file is
  * generated per machine (init, upgrade, SessionStart, `monomind pick`) and is
  * never committed — a shipped snapshot listed skills a project did not have.
- * README/overview/reference docs, `_`-prefixed includes and helper-only
- * skills (HELPER_ONLY, or frontmatter `type: helper`) are not entries.
+ * README/overview/reference docs, internal includes (any `_`-prefixed file,
+ * folder or frontmatter `name`) and helper-only skills (HELPER_ONLY, or
+ * frontmatter `type: helper`) are not entries.
  * Frontmatter `pick: low` marks an admin/meta entry (org management pages,
  * examples, the picker itself): it stays in the index, recorded as
  * `pick: 'low'`, and the pickers rank it below equally matching entries so
@@ -35,10 +36,11 @@ var os = require('os');
 var path = require('path');
 var orgIndex = require('./org-skill-index.cjs');
 
-/** Protocol pieces other skills include; never invoked on their own. */
+/** Protocol pieces other skills include; never invoked on their own.
+ *  (`_`-prefixed includes need no entry here: isNotACandidate skips them all.) */
 var HELPER_ONLY = new Set([
   'mastermind-agent-select', 'mastermind-delegation', 'mastermind-intake',
-  'mastermind-protocol', 'mastermind-repeat', '_repeat', '_taskfile',
+  'mastermind-protocol', 'mastermind-repeat',
 ]);
 /** Documentation pages that live beside commands but are not commands. */
 var DOC_NAMES = new Set(['readme', 'overview', 'reference', 'references']);
@@ -167,11 +169,13 @@ function isJunk(basename) {
 }
 
 /** Docs and helper-only pieces: README/overview/reference pages (or anything
- *  under a references/ dir), HELPER_ONLY names, and `type: helper` frontmatter. */
+ *  under a references/ dir), internal includes (a `_`-prefixed path segment or
+ *  frontmatter name), HELPER_ONLY names, and `type: helper` frontmatter. */
 function isNotACandidate(parts, fm) {
   for (var i = 0; i < parts.length; i++) {
-    if (DOC_NAMES.has(parts[i].toLowerCase())) return true;
+    if (DOC_NAMES.has(parts[i].toLowerCase()) || parts[i].charAt(0) === '_') return true;
   }
+  if (String(fm.name || '').trim().charAt(0) === '_') return true;
   if (HELPER_ONLY.has(parts[parts.length - 1])) return true;
   return String(fm.type || '').toLowerCase() === 'helper';
 }

package/.claude/helpers/handlers/pick-core.cjs

@@ -18,20 +18,17 @@ try { redaction = require('../redact-secrets.cjs'); } catch (e) { /* preview fal
 var pickStats = null;
 try { pickStats = require('../pick-stats.cjs'); } catch (e) { /* no outcome prior: keyword order stands */ }
 var pickRank = null;
-try { pickRank = require('../pick-rank.cjs'); } catch (e) { /* no trivial-prompt check */ }
-
-// A keyword pick needs this score (pick-rank.cjs: idf-weighted BM25 times the
-// share of task words matched) AND a lead of KEYWORD_AGENT_LEAD over the
-// runner-up. Ties and weak overlap print nothing: a wrong pick in Claude's
-// context costs more than none. Tuned on the 40-task pick benchmark: 25/40
-// shown, 23 of them correct.
-var KEYWORD_MIN_AGENT_SCORE = 2;
-var KEYWORD_AGENT_LEAD = 1.5;
-// A keyword skill pick (pick-rank.cjs over the shared skill catalog) needs
-// this score AND a KEYWORD_SKILL_LEAD lead over the runner-up. Calibrated on
-// tests/pick-eval (59 tasks, 514 skills): 34 shown, 31 of them correct (91%).
-var KEYWORD_MIN_SKILL_SCORE = 3;
-var KEYWORD_SKILL_LEAD = 1.25;
+try { pickRank = require('../pick-rank.cjs'); } catch (e) { /* no trivial-prompt check, no keyword pick */ }
+
+// A keyword pick needs a minimum score (pick-rank.cjs: idf-weighted BM25 times
+// the share of task words matched) AND a lead over the runner-up: the one
+// gate pick-rank.cjs defines (KEYWORD_GATE, leads) and the CLI's `pick`
+// shares. Without pick-rank nothing clears it.
+var GATE = (pickRank && pickRank.KEYWORD_GATE) || { agents: { min: Infinity, lead: 1 }, skills: { min: Infinity, lead: 1 } };
+var KEYWORD_MIN_AGENT_SCORE = GATE.agents.min;
+var KEYWORD_AGENT_LEAD = GATE.agents.lead;
+var KEYWORD_MIN_SKILL_SCORE = GATE.skills.min;
+var KEYWORD_SKILL_LEAD = GATE.skills.lead;
 var MAX_CANDIDATES = 5;
 var PREVIEW_CHARS = 120;
 // A prompt with fewer content words ("hi", "thanks", "ok, go ahead") is a
@@ -131,20 +128,18 @@ function rankSkills(jp, prompt, skills) {
     });
 }
 
-/** The top entry when it clears `min` and leads the runner-up by `ratio`. The
- *  floor is on keyword relevance alone (baseScore when a prior re-ranked). */
+/** pick-rank.cjs leads(): the top entry when it clears the gate. */
 function leads(list, min, ratio) {
-  var top = list && list[0];
-  if (!top || !((top.baseScore !== undefined ? top.baseScore : top.score) >= min)) return null;
-  var second = list[1];
-  if (!second || !(second.score > 0)) return top;
-  return top.score >= second.score * (ratio || 1) && top.score > second.score ? top : null;
+  return pickRank ? pickRank.leads(list, min, ratio) : null;
 }
 
 /**
  * The prompt's pick. A Jev agent answer (already past acceptAgent) wins, else a
  * strong keyword agent; a confident Jev skill answer (including "none fits")
- * wins, else a strong keyword skill. Agent ids are resolved to registry names.
+ * wins, else a strong keyword skill. A question Jev answered below its bar
+ * (agentResponded / skillResponded) gets no pick at all: its candidates held
+ * the keyword leaders and it did not back them. Agent ids are resolved to
+ * registry names.
  */
 function decide(opts) {
   var agents = opts.agents || [];
@@ -159,6 +154,8 @@ function decide(opts) {
     out.agent = { id: jev.agent, name: byId[jev.agent].name };
     out.confidence = jev.agentConfidence;
     viaJev = true;
+  } else if (jev && jev.agentResponded) {
+    viaJev = true;
   } else {
     var kw = leads(opts.keywordCands, KEYWORD_MIN_AGENT_SCORE, KEYWORD_AGENT_LEAD);
     if (kw) { out.agent = { id: kw.id, name: kw.name }; viaKeyword = true; }
@@ -168,6 +165,8 @@ function decide(opts) {
     var js = (jev.skills || [])[0];
     if (js) out.skill = { skill: js.id, invoke: js.invoke };
     viaJev = true;
+  } else if (jev && jev.skillResponded) {
+    viaJev = true;
   } else {
     var ks = leads(opts.skillMatches, KEYWORD_MIN_SKILL_SCORE, KEYWORD_SKILL_LEAD);
     if (ks) { out.skill = { skill: ks.skill, invoke: ks.invoke }; viaKeyword = true; }
@@ -185,11 +184,23 @@ function decide(opts) {
   return out;
 }
 
-/** The one line Claude sees: `[PICK] agent: <name> · skill: <invoke>`, '' when nothing is confident. */
+var ORG_SKILL_INVOKE = 'mcp__monomind__org_skill_show ';
+
+/** The one line Claude sees: `[PICK] agent: <name> · skill: <invoke>`, '' when
+ *  nothing is confident. An Org skill also names its CLI read: Claude Code
+ *  keeps a running MCP server until restart, and one older than the
+ *  org_skill_show tool fails the MCP call. */
 function formatPickLine(pick) {
   var parts = [];
   if (pick && pick.agent) parts.push('agent: ' + pick.agent.name);
-  if (pick && pick.skill) parts.push('skill: ' + pick.skill.invoke);
+  if (pick && pick.skill) {
+    var invoke = pick.skill.invoke;
+    // Only a plain skill name (the org_skill_show name rule) goes into a command line.
+    if (invoke.indexOf(ORG_SKILL_INVOKE) === 0 && /^[a-z0-9][a-z0-9-]{0,63}$/.test(pick.skill.skill || '')) {
+      invoke += ' (or: npx -y monomind org skills show ' + pick.skill.skill + ')';
+    }
+    parts.push('skill: ' + invoke);
+  }
   return parts.length ? '[PICK] ' + parts.join(' · ') : '';
 }
 

package/.claude/helpers/handlers/route-handler.cjs

@@ -120,9 +120,12 @@ async function _pickWithJev(CWD, prompt, agents, includeAgentId, skills) {
   return {
     provider: picked.provider,
     agent: jp.acceptAgent(picked.agent),
+    // Jev answered the question (at any confidence): no keyword pick replaces it.
+    agentResponded: !!picked.agent,
     agentConfidence: picked.agent ? picked.agent.confidence : 0,
     agentRanked: picked.agent ? picked.agent.ranked : [],
-    // Only a confident skill answer (including a confident "none fits") replaces keyword matches.
+    skillResponded: !!picked.skill,
+    // Only a confident skill answer (including a confident "none fits") names a skill.
     skillAnswered: !!picked.skill && picked.skill.confidence >= jp.resolveMinConfidence(process.env),
     skills: jp.acceptSkills(picked.skill).map(function (id) { return skillById[id]; }).filter(Boolean),
   };
@@ -134,6 +137,10 @@ async function _pickWithJev(CWD, prompt, agents, includeAgentId, skills) {
 // is not a selector (its agent table and matchSkills predate the catalogs).
 async function _decidePick(CWD, prompt) {
   var jp = _loadJevPicker();
+  // The skill index is read below: rebuild it first when a skill/command tree
+  // is newer (a stat scan, plus a ~30 ms build only when stale). Fails open:
+  // the catalog still drops entries whose file is gone.
+  try { pickCore.ensureSkillRegistryFresh(CWD); } catch (e) { /* keep the index as it is */ }
   var agents = jp ? jp.loadAgentCatalog(CWD) : [];
   var skills = jp ? jp.loadSkillCatalog(CWD) : [];
   var skillMatches = pickCore.rankSkills(jp, prompt, skills);
@@ -144,8 +151,9 @@ async function _decidePick(CWD, prompt) {
   var keywordCands = pickCore.rankAgents(jp, prompt, agents, stats);
   var jev = await _pickWithJev(CWD, prompt, agents, keywordCands[0] && keywordCands[0].id, skills);
   var pick = pickCore.decide({ agents: agents, keywordCands: keywordCands, skillMatches: skillMatches, jev: jev });
-  // Jev's skill answer replaces keyword skill matches, including "none fits".
-  if (jev && jev.skillAnswered) {
+  // Jev's skill answer replaces keyword skill matches, including "none fits"
+  // and an answer below its bar (no skills then).
+  if (jev && jev.skillResponded) {
     skillMatches = jev.skills.map(function (s, i) {
       return { skill: s.id, invoke: s.invoke, description: s.description || '', score: i === 0 ? 2 : 1, source: 'jev' };
     });

package/.claude/helpers/hook-handler.cjs

@@ -313,8 +313,10 @@ async function main() {
   function isSimpleCommand(p) {
     if (typeof p !== 'string') return false;
     var s = p.trim();
-    // Slash commands: /ts, /list-agents, /commit, /help, /use-agent etc.
-    if (/^\/[a-z0-9_-]+(\s|$)/i.test(s)) return true;
+    // Slash commands: /ts, /list-agents, /commit, /help, and namespaced ones
+    // (/mastermind:plan). A path (/var/log/app.log …) has a second '/' and is
+    // not a command.
+    if (/^\/[a-z0-9_-]+(:[a-z0-9_-]+)*(\s|$)/i.test(s)) return true;
     // Short single-word operator tokens (toggle, list, status)
     if (/^(ts|ls|ps|pwd|help|clear|exit|quit|status|toggle|refresh)$/i.test(s)) return true;
     // Already-resolved command messages (Claude Code sends hook with command-name context)

package/.claude/helpers/jev-catalog.cjs

@@ -49,7 +49,9 @@ function norm(s) {
 
 /** Agents from .monomind/registry.json (built by registry-builder.ts), or from
  *  opts.registry (an in-memory build outside a project). The description leads
- *  with the one-line `when_to_use`; deprecated agents drop. */
+ *  with the one-line `when_to_use`; deprecated agents drop. The `vibe`
+ *  personality line is not ranked: its words ("crashes", "segfault") name no
+ *  capability and pulled unrelated tasks to the agent. */
 function loadAgentCatalog(root, opts) {
   var reg = (opts && opts.registry) || readJsonFile(path.join(root, '.monomind', 'registry.json'));
   var list = reg && Array.isArray(reg.agents) ? reg.agents : [];
@@ -67,7 +69,7 @@ function loadAgentCatalog(root, opts) {
       category: category,
       description: when ? when + (description ? ' — ' + description : '') : description,
       text: [category]
-        .concat(strings(a.tags), strings(a.capabilities), strings(a.taskTypes), typeof a.vibe === 'string' ? [a.vibe] : [])
+        .concat(strings(a.tags), strings(a.capabilities), strings(a.taskTypes))
         .filter(Boolean)
         .join(' '),
     };
@@ -143,11 +145,13 @@ function jevAllowed(gate, s, root) {
 }
 
 /** Platform commands/skills. Command/skill mirrors of one capability collapse,
- *  preferring the slash form. */
+ *  preferring the slash form. An entry whose source file is gone (the index
+ *  predates its removal) is dropped: naming it would fail at invoke time. */
 function platformSkills(root, list, gate) {
   var byKey = new Map();
   list.forEach(function (s) {
     if (!s || typeof s.skill !== 'string' || typeof s.invoke !== 'string') return;
+    if (typeof s.source === 'string' && !fs.existsSync(sourceFile(root, s.source))) return;
     // A catalog projection reaches the decision model only when approved with
     // the jev target; ordinary skills carry no catalog field and are unaffected.
     if (s.catalog && s.catalog.jev !== true) return;