npm - monomind - Versions diffs - 2.5.1 → 2.5.2 - Mend

monomind 2.5.1 → 2.5.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (289) hide show

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

@@ -21,7 +21,7 @@ This skill is invoked by `mastermind:stoporg` or directly via `/mastermind:stopo
 ## 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`.
 ---
@@ -144,4 +144,4 @@ next_actions:
 ## 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/taskdev.md → mastermind-taskdev/SKILL.md} RENAMED Viewed

@@ -49,7 +49,7 @@ digraph when_to_use {
 ## Inputs
-- `brain_context`: BRAIN CONTEXT block (loaded via _protocol.md brain load)
+- `brain_context`: BRAIN CONTEXT block (loaded via mastermind-protocol/SKILL.md brain load)
 - `plan_file`: absolute path to the plan `.md` file to execute
 - `params`: any additional flags or context
 - `mode`: auto | confirm
@@ -366,12 +366,12 @@ Done!
 ## Integration
 **Required workflow skills:**
-- `Skill("mastermind-skills:plan")` - Creates the plan this skill executes
-- `Skill("mastermind-skills:review")` - Code review template for reviewer subagents
-- `Skill("mastermind-skills:finish")` - Complete development after all tasks done
+- `Skill("mastermind-plan")` - Creates the plan this skill executes
+- `Skill("mastermind-review")` - Code review template for reviewer subagents
+- `Skill("mastermind-finish")` - Complete development after all tasks done
 **Subagents should use:**
-- `Skill("mastermind-skills:tdd")` - Subagents follow TDD for each task
+- `Skill("mastermind-tdd")` - Subagents follow TDD for each task
 **Alternative workflow:**
-- `Skill("mastermind-skills:execute")` - Use for parallel session instead of same-session execution
+- `Skill("mastermind-execute")` - Use for parallel session instead of same-session execution

package/packages/@monomind/cli/.claude/skills/{mastermind-skills → mastermind-taskdev}/implementer-prompt.md RENAMED Viewed

@@ -30,7 +30,7 @@ Task tool (general-purpose):
     Once you're clear on requirements:
     1. Implement exactly what the task specifies
-    2. Write tests following TDD (use Skill("mastermind-skills:tdd") if available)
+    2. Write tests following TDD (use Skill("mastermind-tdd") if available)
     3. Verify implementation works
     4. Commit your work
     5. Self-review (see below)

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

@@ -28,7 +28,7 @@ This skill is invoked by `mastermind:tasks` or directly via `/mastermind:tasks`.
 ## 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`.
 ---
@@ -149,4 +149,4 @@ task_id: <task_id if applicable>
 ## 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/tdd.md → mastermind-tdd/SKILL.md} RENAMED Viewed

@@ -19,7 +19,7 @@ Write the test first. Watch it fail. Write minimal code to pass.
 ## 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`: what feature or bug to implement with TDD
 - `project_name`: monotask space name
 - `board_id`: monotask board ID (set by master, or created standalone)
@@ -137,7 +137,7 @@ Confirm:
 **Test errors?** Fix error, re-run until it fails correctly.
-Invoke `Skill("mastermind-skills:verify")` to gate this step: the RED verification must confirm the test fails for the expected reason.
+Invoke `Skill("mastermind-verify")` to gate this step: the RED verification must confirm the test fails for the expected reason.
 ### GREEN — Minimal Code
@@ -192,7 +192,7 @@ Confirm:
 **Other tests fail?** Fix now.
-Invoke `Skill("mastermind-skills:verify")` to gate this step.
+Invoke `Skill("mastermind-verify")` to gate this step.
 ### REFACTOR — Clean Up
@@ -350,7 +350,7 @@ Extract validation for multiple fields if needed.
 ## Verification Checklist
-Before marking work complete — invoke `Skill("mastermind-skills:verify")` to run this gate:
+Before marking work complete — invoke `Skill("mastermind-verify")` to run this gate:
 - [ ] Every new function/method has a test
 - [ ] Watched each test fail before implementing

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

@@ -1,5 +1,5 @@
 ---
-name: mastermind:techport
+name: mastermind-techport
 description: Tech Port — deep-analyzes a foreign project, reviews the current monomind target to avoid conflicts and duplication, produces a scored port plan with mono-branded naming, and executes approved ports with full brand normalization.
 type: domain-skill
 default_mode: confirm
@@ -14,10 +14,10 @@ Five-phase porting skill. Phases 0–1 run in parallel. Phase 2 builds the gap m
 ## Standalone Execution
 If invoked directly (not by `mastermind:master`):
-1. Load brain context following `_protocol.md` Brain Load Procedure (namespace: `techport`)
+1. Load brain context following `mastermind-protocol/SKILL.md` Brain Load Procedure (namespace: `techport`)
 2. Parse `source_path`, `focus_hint`, `mode` from user input
 3. Proceed with Phase 0 below
-4. At the end of every run — regardless of which phase concluded — execute `_protocol.md` Brain Write Procedure, writing output to namespace `mastermind:techport:raw`. This includes Phase 1A license-gate STOPs and secrets STOPs. Never skip Brain Write.
+4. At the end of every run — regardless of which phase concluded — execute `mastermind-protocol/SKILL.md` Brain Write Procedure, writing output to namespace `mastermind:techport:raw`. This includes Phase 1A license-gate STOPs and secrets STOPs. Never skip Brain Write.
 ---
@@ -726,10 +726,10 @@ NEXT STEPS
 ## Output Schema (Brain Write — mastermind:master compatible)
-After Phase 3 (analysis) or Phase 5 (execution), write brain output using `_protocol.md` Unified Output Schema — the required fields must be present exactly, with techport-specific data embedded in `artifacts` and `decisions`:
+After Phase 3 (analysis) or Phase 5 (execution), write brain output using `mastermind-protocol/SKILL.md` Unified Output Schema — the required fields must be present exactly, with techport-specific data embedded in `artifacts` and `decisions`:
 ```yaml
-# _protocol.md Unified Output Schema — namespace: mastermind:techport:raw
+# mastermind-protocol/SKILL.md Unified Output Schema — namespace: mastermind:techport:raw
 domain: techport
 status: analysis_complete | port_complete | blocked
 artifacts:

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

@@ -27,7 +27,7 @@ This skill is invoked by `mastermind:threads` or directly via `/mastermind:threa
 ## 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`.
 ---
@@ -256,4 +256,4 @@ thread_id: <thread_id or new_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`.

package/packages/@monomind/cli/.claude/skills/{mastermind-skills/tree-control.md → mastermind-tree-control/SKILL.md} RENAMED Viewed

@@ -34,7 +34,7 @@ All tree-control actions must respect these invariants:
 ## 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 @@ issue_id: <issue_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`.

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

@@ -19,7 +19,7 @@ Claiming work is complete without verification is dishonesty, not efficiency.
 ## 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`: what to verify and what claim is being made
 - `project_name`: monotask space name
 - `board_id`: monotask board ID (set by master, or created standalone)

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

@@ -46,7 +46,7 @@ This skill is invoked by `mastermind:wiki` or directly via `/mastermind:wiki`.
 ## 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`.
 ---
@@ -311,4 +311,4 @@ wiki_root: .monomind/orgs/<org_name>/wiki/
 ## 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/workspace-detail.md → mastermind-workspace-detail/SKILL.md} RENAMED Viewed

@@ -43,7 +43,7 @@ This skill is invoked by `mastermind:workspace-detail` or directly via `/masterm
 ## 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`.
 ---
@@ -314,4 +314,4 @@ workspace_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/workspaces.md → mastermind-workspaces/SKILL.md} RENAMED Viewed

@@ -46,7 +46,7 @@ A workspace is a git worktree assigned to a project, optionally running services
 ## 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`.
 ---
@@ -258,4 +258,4 @@ workspaces_total: <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`.