monomind 2.5.0 → 2.5.2

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/createorg.md → mastermind-createorg/SKILL.md}

@@ -29,11 +29,11 @@ Org Runtime v2 (`packages/@monomind/cli/src/orgrt/`) is a Node daemon, not a Tas
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command" (i.e. invoked directly, not by the command wrapper), load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command" (i.e. invoked directly, not by the command wrapper), load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 If `caller` is "command", use the `brain_context` already provided.
 
-Run intake from `_intake.md` if `prompt` is vague (stop at Q3, domain is `ops`). Skip intake if `prompt` is a rich prompt per _intake.md criteria.
+Run intake from `mastermind-intake/SKILL.md` if `prompt` is vague (stop at Q3, domain is `ops`). Skip intake if `prompt` is a rich prompt per mastermind-intake/SKILL.md criteria.
 
 ---
 
@@ -244,4 +244,4 @@ If `schedule` was set, also print:
 
 ## Step 7 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/debug.md → mastermind-debug/SKILL.md}

@@ -157,7 +157,7 @@ Once you understand WHERE the break is, find existing working examples:
 
 1. **Write a failing test first** (before touching production code)
    - Automated test where possible; a one-off test script if no framework
-   - Use `Skill("mastermind-skills:tdd")` for writing proper failing tests
+   - Use `Skill("mastermind-tdd")` for writing proper failing tests
    - The test MUST fail before the fix proves it
 
 2. **Implement a single fix**
@@ -170,7 +170,7 @@ Once you understand WHERE the break is, find existing working examples:
    - Test passes now?
    - No other tests broken?
    - Issue actually resolved?
-   - Use `Skill("mastermind-skills:review")` to verify before declaring done
+   - Use `Skill("mastermind-review")` to verify before declaring done
 
 4. **If the fix doesn't work:**
    - STOP
@@ -266,8 +266,8 @@ If systematic investigation reveals the issue is truly environmental, timing-dep
 - **Condition-based waiting:** replace arbitrary sleeps/timeouts in flaky tests and scripts with polling for the actual condition ("wait until the file exists / the port answers"), with a hard cap. Timing guesses are bugs waiting for a slower machine.
 
 **Related skills:**
-- `Skill("mastermind-skills:tdd")` — for creating the failing test case (Phase 4, Step 1)
-- `Skill("mastermind-skills:verify")` — verify the fix worked before claiming success
+- `Skill("mastermind-tdd")` — for creating the failing test case (Phase 4, Step 1)
+- `Skill("mastermind-verify")` — verify the fix worked before claiming success
 
 ## Impact
 

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/_delegation.md → mastermind-delegation/SKILL.md}

@@ -1,6 +1,6 @@
 ---
 name: mastermind-delegation
-description: Agent Delegation Capability — injected into every spawned agent prompt so subagents can further delegate specialized work. Never invoked directly; referenced by _protocol.md and domain skills.
+description: Agent Delegation Capability — injected into every spawned agent prompt so subagents can further delegate specialized work. Never invoked directly; referenced by mastermind-protocol/SKILL.md and domain skills.
 type: shared
 ---
 

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/design.md → mastermind-design/SKILL.md}

@@ -25,7 +25,7 @@ Every feature goes through this process. A todo list, a single-function utility,
 
 ## Inputs
 
-- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via _protocol.md brain load)
+- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via mastermind-protocol/SKILL.md brain load)
 - `prompt`: the idea or request to design
 - `project_name`: project context
 - `mode`: auto | confirm
@@ -44,7 +44,7 @@ Complete these items in order:
 6. **Write design doc** — save to `docs/mastermind/specs/YYYY-MM-DD-<topic>-design.md`
 7. **Spec self-review** — inline check for placeholders, contradictions, ambiguity, scope (see below)
 8. **User reviews written spec** — ask user to review before proceeding
-9. **Transition to planning** — invoke `Skill("mastermind-skills:plan")` to create the implementation plan
+9. **Transition to planning** — invoke `Skill("mastermind-plan")` to create the implementation plan
 
 ---
 
@@ -67,10 +67,10 @@ Spec self-review (fix inline)
         ↓
 User reviews spec? → changes requested → Write design doc
         ↓ approved
-Invoke Skill("mastermind-skills:plan")  ← TERMINAL STATE
+Invoke Skill("mastermind-plan")  ← TERMINAL STATE
 ```
 
-**The terminal state is invoking `Skill("mastermind-skills:plan")`.** Do NOT invoke mastermind:build or any other implementation skill directly. The ONLY next step after design is plan.
+**The terminal state is invoking `Skill("mastermind-plan")`.** Do NOT invoke mastermind:build or any other implementation skill directly. The ONLY next step after design is plan.
 
 ---
 
@@ -142,11 +142,11 @@ Fix any issues inline. No need to re-review — just fix and move on.
 
 Wait for the user's response. If they request changes, make them and re-run the spec self-review. Only proceed once the user approves.
 
-**In auto mode:** Skip the wait. Proceed directly to `Skill("mastermind-skills:plan")`.
+**In auto mode:** Skip the wait. Proceed directly to `Skill("mastermind-plan")`.
 
 ### Transition to Planning
 
-- Invoke `Skill("mastermind-skills:plan")` to create a detailed implementation plan
+- Invoke `Skill("mastermind-plan")` to create a detailed implementation plan
 - Do NOT invoke any other skill. `mastermind:plan` is the only next step.
 
 ---
@@ -179,12 +179,12 @@ A browser-based companion for showing mockups, diagrams, and visual options duri
 
 A question about a UI topic is not automatically a visual question. "What does personality mean in this context?" is a conceptual question — use the terminal. "Which wizard layout works better?" is a visual question — use the browser.
 
-If they agree to the companion, use `Skill("mastermind-skills:worktree")` to set up an isolated workspace, then invoke `Skill("agent-browser-testing")` to open the browser.
+If they agree to the companion, use `Skill("mastermind-worktree")` to set up an isolated workspace, then invoke `Skill("agent-browser-testing")` to open the browser.
 
 ---
 
 ## Integration
 
 **Skills used by this skill:**
-- `Skill("mastermind-skills:plan")` — creates the implementation plan after design is approved (terminal state)
-- `Skill("mastermind-skills:worktree")` — isolated workspace for visual companion work
+- `Skill("mastermind-plan")` — creates the implementation plan after design is approved (terminal state)
+- `Skill("mastermind-worktree")` — isolated workspace for visual companion work

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/diagnose.md → mastermind-diagnose/SKILL.md}

@@ -36,7 +36,7 @@ If a proposed fix violates any invariant, drop it or rework it. State explicitly
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -246,4 +246,4 @@ invariants:
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/env.md → mastermind-env/SKILL.md}

@@ -25,7 +25,7 @@ This skill is invoked by `mastermind:env` or directly via `/mastermind:env`.
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -200,4 +200,4 @@ validation_errors: <N>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/environments.md → mastermind-environments/SKILL.md}

@@ -39,7 +39,7 @@ This skill is invoked by `mastermind:environments` or directly via `/mastermind:
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -247,4 +247,4 @@ default_env: <id or null>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/execute.md → mastermind-execute/SKILL.md}

@@ -11,13 +11,13 @@ Load plan, review critically, execute all tasks, report when complete.
 
 **Announce at start:** "I'm using the mastermind:execute skill to implement this plan."
 
-**Note:** This skill works best with subagent support (Claude Code). When subagents are available, prefer `Skill("mastermind-skills:taskdev")` for parallel task execution.
+**Note:** This skill works best with subagent support (Claude Code). When subagents are available, prefer `Skill("mastermind-taskdev")` for parallel task execution.
 
 ---
 
 ## Inputs
 
-- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via _protocol.md brain load)
+- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via mastermind-protocol/SKILL.md brain load)
 - `plan_path`: path to the plan file to execute
 - `project_name`: monotask space name
 - `board_id`: monotask board ID
@@ -48,16 +48,16 @@ For each task in the plan:
 4. Mark as `completed`
 
 When the plan references skills:
-- `mastermind:taskdev` → invoke `Skill("mastermind-skills:taskdev")`
-- `mastermind:verify` → invoke `Skill("mastermind-skills:verify")`
-- Any other `mastermind:*` skill → invoke `Skill("mastermind-skills:<name>")`
+- `mastermind:taskdev` → invoke `Skill("mastermind-taskdev")`
+- `mastermind:verify` → invoke `Skill("mastermind-verify")`
+- Any other `mastermind:*` skill → invoke `Skill("mastermind-<name>")`
 
 ### Step 3: Complete Development
 
 After all tasks complete and are verified:
 
 - Announce: "All tasks complete. Handing off to mastermind:finish."
-- **REQUIRED SUB-SKILL:** invoke `Skill("mastermind-skills:finish")`
+- **REQUIRED SUB-SKILL:** invoke `Skill("mastermind-finish")`
 - Follow that skill to verify tests, present options, and execute the chosen finish action
 
 ---
@@ -98,7 +98,7 @@ After all tasks complete and are verified:
 ## Integration
 
 **Skills used by this skill:**
-- `Skill("mastermind-skills:plan")` — creates the plan this skill executes
-- `Skill("mastermind-skills:taskdev")` — subagent-driven parallel task execution (preferred for complex plans)
-- `Skill("mastermind-skills:finish")` — complete the development branch after all tasks
-- `Skill("mastermind-skills:verify")` — verification gate before finishing
+- `Skill("mastermind-plan")` — creates the plan this skill executes
+- `Skill("mastermind-taskdev")` — subagent-driven parallel task execution (preferred for complex plans)
+- `Skill("mastermind-finish")` — complete the development branch after all tasks
+- `Skill("mastermind-verify")` — verification gate before finishing

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/export.md → mastermind-export/SKILL.md}

@@ -58,7 +58,7 @@ This skill is invoked by `mastermind:export` or directly via `/mastermind:export
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -330,4 +330,4 @@ collision_strategy: <strategy if import>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/finance.md → mastermind-finance/SKILL.md}

@@ -13,7 +13,7 @@ This skill is invoked by `mastermind:master` or directly via `/mastermind:financ
 
 ## Inputs
 
-- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via _protocol.md brain load)
+- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via mastermind-protocol/SKILL.md brain load)
 - `prompt`: the finance goal for this run
 - `project_name`: monotask space name
 - `board_id`: monotask board ID (set by master, or created standalone)
@@ -43,9 +43,9 @@ Assess the prompt to determine execution mode:
 
 If this skill is invoked directly (not by master):
 
-1. Load brain context following _protocol.md Brain Load Procedure (namespace: `finance`)
-2. Run intake from _intake.md if prompt is vague
-3. Follow _protocol.md Monotask Space+Board Setup Procedure:
+1. Load brain context following mastermind-protocol/SKILL.md Brain Load Procedure (namespace: `finance`)
+2. Run intake from mastermind-intake/SKILL.md if prompt is vague
+3. Follow mastermind-protocol/SKILL.md Monotask Space+Board Setup Procedure:
    ```bash
    project_name="${project_name:-$(basename "$PWD")}"
    space_id=$(monotask space list 2>/dev/null | awk -F' \| ' -v n="$project_name" '$2==n{print $1}' | head -1)
@@ -59,7 +59,7 @@ If this skill is invoked directly (not by master):
    done_col=$(monotask column create "$board_id" "Done"  --json | jq -r '.id')
    ```
 4. Proceed with complexity assessment below
-5. At end: follow _protocol.md Brain Write Procedure (namespace: `finance`)
+5. At end: follow mastermind-protocol/SKILL.md Brain Write Procedure (namespace: `finance`)
 
 ---
 

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/goal-detail.md → mastermind-goal-detail/SKILL.md}

@@ -40,7 +40,7 @@ open → in_progress → done
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -252,4 +252,4 @@ sub_goals: <N>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/goals.md → mastermind-goals/SKILL.md}

@@ -27,7 +27,7 @@ This skill is invoked by `mastermind:goals` or directly via `/mastermind:goals`.
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -146,4 +146,4 @@ Suggest next: "Link tasks to this goal with /mastermind:tasks link or /mastermin
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/heartbeatv1.md → mastermind-heartbeatv1/SKILL.md}

@@ -28,7 +28,7 @@ This skill is invoked by `mastermind:heartbeatv1` or directly via `/mastermind:h
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -164,4 +164,4 @@ Print: "Heartbeat complete for <agentTitle>. Check outputs with: npx monomind@la
 
 ## Step 7 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/idea.md → mastermind-idea/SKILL.md}

@@ -13,7 +13,7 @@ This skill is invoked by `mastermind:master` or directly via `/mastermind:idea`.
 
 **File mode (default, `USE_MONOTASK=false`):**
 
-Invoke `Skill("mastermind-skills:ideate", $ARGUMENTS)` immediately — it provides the same research, evaluation, elaboration, and task-decomposition pipeline with file-first storage (`docs/ideas/` and `docs/tasks/`). The rest of this skill is skipped in file mode.
+Invoke `Skill("mastermind-ideate", $ARGUMENTS)` immediately — it provides the same research, evaluation, elaboration, and task-decomposition pipeline with file-first storage (`docs/ideas/` and `docs/tasks/`). The rest of this skill is skipped in file mode.
 
 **Board mode (`USE_MONOTASK=true`):**
 
@@ -23,7 +23,7 @@ Continue with the full monotask board pipeline below (Steps 3-6).
 
 ## Inputs
 
-- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via _protocol.md brain load)
+- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via mastermind-protocol/SKILL.md brain load)
 - `prompt`: the ideation goal for this run
 - `project_name`: monotask space name
 - `mode`: auto | confirm
@@ -54,10 +54,10 @@ Assess the prompt to determine execution mode:
 
 If this skill is invoked directly (not by master):
 
-1. Load brain context following _protocol.md Brain Load Procedure (namespace: `idea`)
-2. Run intake from _intake.md if prompt is vague
+1. Load brain context following mastermind-protocol/SKILL.md Brain Load Procedure (namespace: `idea`)
+2. Run intake from mastermind-intake/SKILL.md if prompt is vague
 3. For complex prompts: run Steps 3–6 below
-4. At end: follow _protocol.md Brain Write Procedure (namespace: `idea`)
+4. At end: follow mastermind-protocol/SKILL.md Brain Write Procedure (namespace: `idea`)
 
 ---
 
@@ -67,7 +67,7 @@ For simple prompts (single agent, single output):
 
 1. Spawn one Task agent with the ideation request as a self-contained briefing
 2. Collect output
-3. If called standalone (not from master): follow _protocol.md Brain Write Procedure (namespace: `idea`)
+3. If called standalone (not from master): follow mastermind-protocol/SKILL.md Brain Write Procedure (namespace: `idea`)
 4. Return unified output schema with `status: complete`
 
 ---
@@ -1058,7 +1058,7 @@ done < <(echo "$merged_flagged_json" | jq -c '.[]')
 
 ### Step 7 — Brain Write + Return
 
-Follow _protocol.md Brain Write Procedure (namespace: `idea`).
+Follow mastermind-protocol/SKILL.md Brain Write Procedure (namespace: `idea`).
 
 **Write domain output to session file** so master Step 9 aggregation can include this domain. Skip silently if running standalone (no SESSION_ID in current.json):
 

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/import.md → mastermind-import/SKILL.md}

@@ -35,7 +35,7 @@ This skill is invoked by `mastermind:import` or directly via `/mastermind:import
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -278,4 +278,4 @@ collision: <strategy>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/inbox.md → mastermind-inbox/SKILL.md}

@@ -24,7 +24,7 @@ This skill is invoked by `mastermind:inbox` or directly via `/mastermind:inbox`.
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -223,4 +223,4 @@ budget_alerts: <N>
 
 ## Step 5 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/instance.md → mastermind-instance/SKILL.md}

@@ -25,7 +25,7 @@ This skill is invoked by `mastermind:instance` or directly via `/mastermind:inst
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -232,4 +232,4 @@ scheduler_enabled: <true|false>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/instance-settings.md → mastermind-instance-settings/SKILL.md}

@@ -46,7 +46,7 @@ This skill is invoked by `mastermind:instance-settings` or directly via `/master
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -312,4 +312,4 @@ action: <action>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/invite-landing.md → mastermind-invite-landing/SKILL.md}

@@ -38,7 +38,7 @@ This skill is invoked by `mastermind:invite-landing` or directly via `/mastermin
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -224,4 +224,4 @@ role: <role>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/invites.md → mastermind-invites/SKILL.md}

@@ -38,7 +38,7 @@ This skill is invoked by `mastermind:invites` or directly via `/mastermind:invit
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -251,4 +251,4 @@ pending_joins: <N>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/issue-detail.md → mastermind-issue-detail/SKILL.md}

@@ -41,7 +41,7 @@ Recovery actions apply when an issue enters `needs_recovery` state after a faile
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -288,4 +288,4 @@ issue_status: <status>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/issues.md → mastermind-issues/SKILL.md}

@@ -31,7 +31,7 @@ This skill is invoked by `mastermind:issues` or directly via `/mastermind:issues
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -232,4 +232,4 @@ org_name: <org_name>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/join-queue.md → mastermind-join-queue/SKILL.md}

@@ -25,7 +25,7 @@ This skill is invoked by `mastermind:join-queue` or directly via `/mastermind:jo
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -167,4 +167,4 @@ type_filter: <request_type>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/liveness.md → mastermind-liveness/SKILL.md}

@@ -50,7 +50,7 @@ An issue is **stalled** when it is non-terminal but has no:
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -389,4 +389,4 @@ issue_id: <issue_id or all>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/marketing.md → mastermind-marketing/SKILL.md}

@@ -13,7 +13,7 @@ This skill is invoked by `mastermind:master` or directly via `/mastermind:market
 
 ## Inputs
 
-- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via _protocol.md brain load)
+- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via mastermind-protocol/SKILL.md brain load)
 - `prompt`: the marketing goal for this run
 - `project_name`: monotask space name
 - `board_id`: monotask board ID (set by master, or created standalone)
@@ -36,9 +36,9 @@ Before building any task briefing, identify which reference files apply and incl
 In each agent task briefing, add:
 ```
 REFERENCE FILES: Read these before starting:
-- .claude/skills/mastermind/references/persuasion-psychology.md
+- .claude/skills/mastermind-marketing/references/persuasion-psychology.md
 [For copy tasks (landing pages, CTAs, email copy, headlines, subject lines), also read:]
-- .claude/skills/mastermind/references/copywriting-frameworks.md
+- .claude/skills/mastermind-marketing/references/copywriting-frameworks.md
 [For all copy review/edit passes, also read:]
 - .claude/skills/stop-slop/SKILL.md
 - .claude/skills/stop-slop/references/phrases.md
@@ -89,9 +89,9 @@ Assess the prompt to determine execution mode:
 
 If this skill is invoked directly (not by master):
 
-1. Load brain context following _protocol.md Brain Load Procedure (namespace: `marketing`)
-2. Run intake from _intake.md if prompt is vague
-3. Follow _protocol.md Monotask Space+Board Setup Procedure:
+1. Load brain context following mastermind-protocol/SKILL.md Brain Load Procedure (namespace: `marketing`)
+2. Run intake from mastermind-intake/SKILL.md if prompt is vague
+3. Follow mastermind-protocol/SKILL.md Monotask Space+Board Setup Procedure:
    ```bash
    project_name="${project_name:-$(basename "$PWD")}"
    space_id=$(monotask space list 2>/dev/null | awk -F' \| ' -v n="$project_name" '$2==n{print $1}' | head -1)
@@ -105,7 +105,7 @@ If this skill is invoked directly (not by master):
    done_col=$(monotask column create "$board_id" "Done"  --json | jq -r '.id')
    ```
 4. Proceed with complexity assessment below
-5. At end: follow _protocol.md Brain Write Procedure (namespace: `marketing`)
+5. At end: follow mastermind-protocol/SKILL.md Brain Write Procedure (namespace: `marketing`)
 
 ---
 
@@ -150,7 +150,7 @@ monotask card comment add "$BOARD_ID" "$CARD_ID" "CONTEXT: <date> | Project: <pr
 BRAIN MEMORY: [paste most relevant 3-5 brain context excerpts]
 SCOPE: [channel, audience, tone, brand constraints]
 CONSTRAINTS: [brand voice, legal/compliance, budget limits, existing assets]
-REFERENCE FILES: [for copy/content workstreams: .claude/skills/mastermind/references/persuasion-psychology.md; for copy tasks also: .claude/skills/mastermind/references/copywriting-frameworks.md; for copy review/edit: .claude/skills/stop-slop/SKILL.md, .claude/skills/stop-slop/references/phrases.md, .claude/skills/stop-slop/references/structures.md]
+REFERENCE FILES: [for copy/content workstreams: .claude/skills/mastermind-marketing/references/persuasion-psychology.md; for copy tasks also: .claude/skills/mastermind-marketing/references/copywriting-frameworks.md; for copy review/edit: .claude/skills/stop-slop/SKILL.md, .claude/skills/stop-slop/references/phrases.md, .claude/skills/stop-slop/references/structures.md]
 SUCCESS CRITERIA:
 - [ ] [checkable item]
 AGENT: [Content Creator | Email Marketing Specialist | CRO Specialist | Pricing Strategist | Launch Strategist | Competitive Content Strategist | SEO Specialist | Social Media Strategist | Analytics Reporter | Ad Creative Strategist]

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/memory.md → mastermind-memory/SKILL.md}

@@ -58,7 +58,7 @@ Three layers, mirrored to `.monomind/orgs/<org_name>-memory/`:
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -318,4 +318,4 @@ topic: <topic>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/monitor.md → mastermind-monitor/SKILL.md}

@@ -35,7 +35,7 @@ A monitor is a named, forever-running task executor. It polls one or more task s
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following `_protocol.md` Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following `mastermind-protocol/SKILL.md` Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -1108,7 +1108,7 @@ run_id: <SESSION_ID>
 
 ## Step 7 — Brain Write (standalone only)
 
-If `caller` is not "command", follow `_protocol.md` Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow `mastermind-protocol/SKILL.md` Brain Write Procedure for domain `ops`.
 
 ---
 

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/my-issues.md → mastermind-my-issues/SKILL.md}

@@ -25,7 +25,7 @@ This skill is invoked by `mastermind:my-issues` or directly via `/mastermind:my-
 
 ## Step 0 — Brain Load (standalone only)
 
-If `caller` is not "command", load brain context following _protocol.md Brain Load Procedure with namespace: `ops`.
+If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
 
 ---
 
@@ -143,4 +143,4 @@ assignee: <assignee_id>
 
 ## Step 4 — Brain Write (standalone only)
 
-If `caller` is not "command", follow _protocol.md Brain Write Procedure for domain `ops`.
+If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.