monomind 2.7.11 → 2.7.13

package/packages/@monomind/cli/.claude/skills/mastermind-plan/SKILL.md

@@ -1,217 +0,0 @@
----
-name: mastermind-plan
-description: Write comprehensive implementation plans from specs or requirements before touching code. Saves plans to docs/mastermind/plans/. No placeholders — every step has exact file paths, complete code, and expected output.
-type: domain-skill
-default_mode: confirm
----
-
-# Mastermind Plan
-
-## Overview
-
-Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
-
-Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
-
-**Announce at start:** "I'm using the mastermind:plan skill to create the implementation plan."
-
-**Context:** If working in an isolated worktree, it should have been created via the git worktrees workflow at execution time.
-
-**Save plans to:** `docs/mastermind/plans/YYYY-MM-DD-<feature-name>.md`
-- (User preferences for plan location override this default)
-
----
-
-## Inputs
-
-- `brain_context`: BRAIN CONTEXT block (loaded via mastermind-protocol/SKILL.md brain load)
-- `params`: spec text, feature description, or path to spec file
-- `mode`: auto | confirm
-
----
-
-## Scope Check
-
-If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
-
----
-
-## File Structure
-
-Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.
-
-- Design units with clear boundaries and well-defined interfaces. Each file should have one clear responsibility.
-- You reason best about code you can hold in context at once, and your edits are more reliable when files are focused. Prefer smaller, focused files over large ones that do too much.
-- Files that change together should live together. Split by responsibility, not by technical layer.
-- In existing codebases, follow established patterns. If the codebase uses large files, don't unilaterally restructure — but if a file you're modifying has grown unwieldy, including a split in the plan is reasonable.
-
-This structure informs the task decomposition. Each task should produce self-contained changes that make sense independently.
-
----
-
-## Task Right-Sizing
-
-A task is the smallest unit that carries its own test cycle and is worth a fresh reviewer's gate. When drawing task boundaries: fold setup, configuration, scaffolding, and documentation steps into the task whose deliverable needs them; split only where a reviewer could meaningfully reject one task while approving its neighbor. Each task ends with an independently testable deliverable.
-
----
-
-## Bite-Sized Task Granularity
-
-**Each step is one action (2-5 minutes):**
-- "Write the failing test" — step
-- "Run it to make sure it fails" — step
-- "Implement the minimal code to make the test pass" — step
-- "Run the tests and make sure they pass" — step
-- "Commit" — step
-
----
-
-## Plan Document Header
-
-**Every plan MUST start with this header:**
-
-```markdown
-# [Feature Name] Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use `Skill("mastermind-taskdev")` (recommended) or `Skill("mastermind-execute")` to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** [One sentence describing what this builds]
-
-**Architecture:** [2-3 sentences about approach]
-
-**Tech Stack:** [Key technologies/libraries]
-
-## Global Constraints
-
-[The spec's project-wide requirements — version floors, dependency limits,
-naming and copy rules, platform requirements — one line each, with exact
-values copied verbatim from the spec. Every task's requirements implicitly
-include this section.]
-
----
-```
-
----
-
-## Task Structure
-
-````markdown
-### Task N: [Component Name]
-
-**Files:**
-- Create: `exact/path/to/file.py`
-- Modify: `exact/path/to/existing.py:123-145`
-- Test: `tests/exact/path/to/test.py`
-
-**Interfaces:**
-- Consumes: [what this task uses from earlier tasks — exact signatures]
-- Produces: [what later tasks rely on — exact function names, parameter
-  and return types. A task's implementer sees only their own task; this
-  block is how they learn the names and types neighboring tasks use.]
-
-- [ ] **Step 1: Write the failing test**
-
-```python
-def test_specific_behavior():
-    result = function(input)
-    assert result == expected
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `pytest tests/path/test.py::test_name -v`
-Expected: FAIL with "function not defined"
-
-- [ ] **Step 3: Write minimal implementation**
-
-```python
-def function(input):
-    return expected
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `pytest tests/path/test.py::test_name -v`
-Expected: PASS
-
-- [ ] **Step 5: Commit**
-
-```bash
-git add tests/path/test.py src/path/file.py
-git commit -m "feat: add specific feature"
-```
-````
-
----
-
-## No Placeholders
-
-Every step must contain the actual content an engineer needs. These are **plan failures** — never write them:
-- "TBD", "TODO", "implement later", "fill in details"
-- "Add appropriate error handling" / "add validation" / "handle edge cases"
-- "Write tests for the above" (without actual test code)
-- "Similar to Task N" (repeat the code — the engineer may be reading tasks out of order)
-- Steps that describe what to do without showing how (code blocks required for code steps)
-- References to types, functions, or methods not defined in any task
-
----
-
-## Remember
-- Exact file paths always
-- Complete code in every step — if a step changes code, show the code
-- Exact commands with expected output
-- DRY, YAGNI, TDD, frequent commits
-
----
-
-## Self-Review
-
-After writing the complete plan, look at the spec with fresh eyes and check the plan against it. This is a checklist you run yourself — not a subagent dispatch.
-
-**1. Spec coverage:** Skim each section/requirement in the spec. Can you point to a task that implements it? List any gaps.
-
-**2. Placeholder scan:** Search your plan for red flags — any of the patterns from the "No Placeholders" section above. Fix them.
-
-**3. Type consistency:** Do the types, method signatures, and property names you used in later tasks match what you defined in earlier tasks? A function called `clearLayers()` in Task 3 but `clearFullLayers()` in Task 7 is a bug.
-
-If you find issues, fix them inline. No need to re-review — just fix and move on. If you find a spec requirement with no task, add the task.
-
----
-
-## User Review Gate
-
-After self-review:
-
-**In confirm mode (default):** Ask the user to review the written plan before proceeding:
-
-> "Plan written and saved to `docs/mastermind/plans/<filename>.md`. Please review it and let me know if you'd like any changes before we start execution."
-
-Wait for the user's response. If they request changes, make them inline and re-run the self-review. Only proceed once the user approves.
-
-**In auto mode:** Skip the wait. Proceed directly to execution handoff.
-
----
-
-## Execution Handoff
-
-After the plan is approved (or in auto mode, after self-review):
-
-**In confirm mode (default):** Ask the user to choose execution mode:
-
-**"Plan complete and saved to `docs/mastermind/plans/<filename>.md`. Two execution options:**
-
-**1. Subagent-Driven (recommended)** — Invoke `Skill("mastermind-taskdev")`: dispatches a fresh subagent per task, reviews between tasks, fast iteration.
-
-**2. Inline Execution** — Invoke `Skill("mastermind-execute")`: batch execution with checkpoints.
-
-**Which approach?"**
-
-**In auto mode:** Skip the question. Default to subagent-driven — invoke `Skill("mastermind-taskdev")` immediately.
-
-**If Subagent-Driven chosen (or auto mode):**
-- Invoke `Skill("mastermind-taskdev")`
-- Fresh subagent per task + two-stage review
-
-**If Inline Execution chosen:**
-- Invoke `Skill("mastermind-execute")`
-- Batch execution with checkpoints for review

package/packages/@monomind/cli/.claude/skills/mastermind-plan-to-tasks/SKILL.md

@@ -1,136 +0,0 @@
----
-name: mastermind-plan-to-tasks
-description: Mastermind plan-to-tasks — converts a written plan (prose, outline, or structured doc) into assigned org issues with correct specialties, dependency wiring, and parallelization. Mirrors Paperclip's plan-to-tasks skill. Use when breaking down a project plan into executable issue trees.
-type: domain-skill
-default_mode: confirm
----
-
-# Mastermind Plan to Tasks
-
-This skill is invoked by `mastermind:plan-to-tasks` or directly via `/mastermind:plan-to-tasks`.
-
----
-
-## Inputs
-
-- `brain_context`: BRAIN CONTEXT block (injected by command, or loaded below if standalone)
-- `org_name`: org to create issues in (required)
-- `plan`: the plan text (required — paste inline or pipe in)
-- `project_id`: assign all issues to this project (optional)
-- `workspace_id`: assign all issues to this workspace (optional)
-- `dry_run`: true | false (default: false — if true, print plan without creating issues)
-- `caller`: command | master
-
----
-
-## Step 0 — Brain Load (standalone only)
-
-If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
-
----
-
-## Step 1 — Validate Inputs
-
-```bash
-[ -z "$org_name" ] && { echo "ERROR: --org required."; exit 1; }
-[ -z "$plan"     ] && { echo "ERROR: --plan required (the plan text to decompose)."; exit 1; }
-
-orgFile=".monomind/orgs/${org_name}.json"
-[ ! -f "$orgFile" ] && { echo "ERROR: Org '${org_name}' not found."; exit 1; }
-```
-
----
-
-## Step 2 — Load Agents for Specialty Matching
-
-```bash
-echo "PLAN-TO-TASKS — $org_name"
-echo "────────────────────────────────────────────────────────"
-echo ""
-echo "AGENTS IN ORG:"
-jq -r '(.roles // [])[] | "  \(.id)  \(.title // "-")  [\(.adapter.type // "?")]"' "$orgFile"
-echo ""
-```
-
----
-
-## Step 3 — Decompose Plan into Issues
-
-Read the plan carefully and apply these rules:
-
-**Planning principles (from Paperclip plan-to-tasks):**
-
-1. **Plan deeply.** Capture real detail: goals, constraints, unknowns, success criteria, risks. A shallow plan becomes rework.
-2. **Know your team.** Read the org's agents and their specialties (titles, roles, adapters) before assigning anything.
-3. **Assign for specialty.** Hand each piece of work to the most relevant agent. If no agent fits, flag the gap.
-4. **Take responsibility.** When you (the AI) are best-suited for a piece, assign it to yourself instead of delegating.
-5. **Use the dependency tree.** Express every concrete deliverable as an issue. Wire real blockers via `blockedByIssueIds`. When done, dependents auto-wake.
-6. **Order, then parallelize.** Sequence by real dependencies. Independent branches start in parallel.
-7. **Enough is enough.** Plans unblock execution. Don't re-plan already clear work.
-
-**Decomposition output:**
-
-For each issue extracted from the plan, produce:
-```
-ISSUE: <title>
-  assignee:    <agent-id or UNASSIGNED>
-  priority:    low | medium | high | urgent
-  blockedBy:   <issue-title> (or none)
-  description: <1-2 sentence summary of the deliverable>
-```
-
-**Quality checklist before creating:**
-- [ ] Enough detail that assignees can act without re-asking
-- [ ] Every concrete deliverable is an issue
-- [ ] Each issue has a deliberate, specialty-matched assignee
-- [ ] Each issue's real blockers are declared
-- [ ] Independent branches can start in parallel
-- [ ] Gaps (missing skills, decisions, external inputs) are surfaced, not hidden
-
----
-
-## Step 4 — Create Issues (unless dry_run=true)
-
-```bash
-issuesFile=".monomind/orgs/${org_name}-issues.json"
-[ ! -f "$issuesFile" ] && echo '{"issues":[]}' > "$issuesFile"
-
-ts=$(date -u +%Y-%m-%dT%H:%M:%SZ)
-
-# Issues are created from the decomposition above
-# Each issue gets:
-#   id: issue-<timestamp>-<N>
-#   title, description, priority, status: open
-#   assigneeId (from matched agent)
-#   projectId, workspaceId (if provided)
-#   blockedByIssueIds (resolved after all issues are created)
-#   createdAt, updatedAt
-
-echo ""
-if [ "${dry_run:-false}" = "true" ]; then
-  echo "DRY RUN — no issues were created."
-  echo "Remove --dry-run to create these issues."
-else
-  echo "CREATED ISSUES:"
-  # (issue creation happens inline above as each issue is decomposed)
-fi
-```
-
----
-
-## Step 5 — Return Output
-
-```yaml
-domain: ops
-status: complete
-action: plan-to-tasks
-org_name: <org_name>
-issues_created: <N>
-dry_run: <true|false>
-```
-
----
-
-## Step 6 — Brain Write (standalone only)
-
-If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.

package/packages/@monomind/cli/.claude/skills/mastermind-plugin-manager/SKILL.md

@@ -1,241 +0,0 @@
----
-name: mastermind-plugin-manager
-description: Mastermind plugin-manager — install plugins from npm, uninstall with two-step confirmation, enable/disable installed plugins. Extends mastermind:plugins (listing) and mastermind:plugin-settings (per-plugin config) with the install/uninstall lifecycle. Mirrors PluginManager.tsx.
-type: domain-skill
-default_mode: confirm
----
-
-# Mastermind Plugin Manager
-
-This skill is invoked by `mastermind:plugin-manager` or directly via `/mastermind:plugin-manager`.
-
----
-
-## Inputs
-
-- `brain_context`: BRAIN CONTEXT block (injected by command, or loaded below if standalone)
-- `action`: list | install | uninstall | enable | disable | check-updates
-- `package_name`: npm package name to install (for install; e.g. `@monomind/plugin-github`)
-- `plugin_id`: plugin id slug (required for uninstall/enable/disable)
-- `confirm`: yes (required second step for uninstall — prevents accidental removal)
-- `caller`: command | master
-
----
-
-## Plugin Record Schema
-
-```json
-{
-  "id": "plugin-slug",
-  "packageName": "@monomind/plugin-name",
-  "status": "installed",
-  "version": "1.2.0",
-  "category": "monitoring",
-  "description": "One-line plugin description",
-  "installedAt": "2026-01-01T00:00:00Z",
-  "config": {},
-  "grants": [],
-  "health": {"status": "ok", "lastCheck": null}
-}
-```
-
----
-
-## Step 0 — Brain Load (standalone only)
-
-If `caller` is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: `ops`.
-
----
-
-## Step 1 — Load Plugin Registry
-
-```bash
-registryFile=".monomind/plugins/registry.json"
-mkdir -p ".monomind/plugins"
-[ ! -f "$registryFile" ] && echo '{"plugins":[]}' > "$registryFile"
-```
-
----
-
-## Step 2 — Execute Action
-
-### list (default)
-
-```bash
-echo "INSTALLED PLUGINS"
-echo "────────────────────────────────────────────────────────"
-printf "%-24s %-10s %-10s %-14s %s\n" "ID" "STATUS" "VERSION" "CATEGORY" "PACKAGE"
-echo "────────────────────────────────────────────────────────"
-
-count=$(jq '.plugins | length' "$registryFile")
-if [ "$count" -eq 0 ]; then
-  echo "  No plugins installed."
-  echo "  Install one: --action install --package-name @monomind/plugin-github"
-else
-  jq -r '(.plugins // [])[] |
-    [.id, (.status // "installed"), (.version // "-"), (.category // "general"),
-     (.packageName // "-")] | @tsv' \
-    "$registryFile" | while IFS=$'\t' read -r id st ver cat pkg; do
-    printf "%-24s %-10s %-10s %-14s %s\n" "$id" "$st" "$ver" "$cat" "$pkg"
-  done
-
-  errCount=$(jq '[(.plugins // [])[] | select(.status == "error")] | length' "$registryFile")
-  [ "$errCount" -gt 0 ] && echo "" && echo "  WARNING: $errCount plugin(s) in error state. Run: --action list to inspect."
-fi
-
-echo ""
-echo "  Install:    --action install --package-name <npm-package>"
-echo "  Uninstall:  --action uninstall --plugin-id <id>"
-echo "  Settings:   /mastermind:plugin-settings --plugin-id <id>"
-```
-
-### install
-
-```bash
-[ -z "$package_name" ] && { echo "ERROR: --package-name required (e.g. @monomind/plugin-github)."; exit 1; }
-
-echo "INSTALLING PLUGIN — $package_name"
-echo "────────────────────────────────────────────────────────"
-echo "  Running: npm install $package_name"
-
-# Check if already installed
-alreadyId=$(jq -r --arg pkg "$package_name" '(.plugins // [])[] | select(.packageName == $pkg) | .id' "$registryFile" | head -1)
-[ -n "$alreadyId" ] && {
-  echo "  Plugin already installed as '$alreadyId'. Use --action enable/disable or reinstall via npm."
-  exit 0
-}
-
-if npm install "$package_name" 2>&1 | tail -5; then
-  # Derive plugin metadata from npm package
-  pkgVer=$(node -e "try{console.log(require('${package_name}/package.json').version)}catch(e){console.log('0.0.0')}" 2>/dev/null || echo "0.0.0")
-  pkgDesc=$(node -e "try{console.log(require('${package_name}/package.json').description||'')}catch(e){console.log('')}" 2>/dev/null || echo "")
-  pluginId=$(echo "$package_name" | sed 's|@[^/]*/||' | tr '[:upper:]' '[:lower:]' | tr -cs 'a-z0-9' '-' | sed 's/^-//;s/-$//')
-  ts=$(date -u +%Y-%m-%dT%H:%M:%SZ)
-
-  tmp="${registryFile}.tmp"
-  jq --arg id "$pluginId" \
-     --arg pkg "$package_name" \
-     --arg ver "$pkgVer" \
-     --arg desc "$pkgDesc" \
-     --arg ts "$ts" \
-    '.plugins += [{"id":$id,"packageName":$pkg,"status":"installed","version":$ver,
-      "description":$desc,"category":"general","config":{},"grants":[],
-      "health":{"status":"ok","lastCheck":null},"installedAt":$ts}]' \
-    "$registryFile" > "$tmp" && mv "$tmp" "$registryFile"
-
-  echo ""
-  echo "Plugin installed: $pluginId @ $pkgVer"
-  echo "  Configure: /mastermind:plugin-settings --plugin-id $pluginId"
-else
-  echo "  ERROR: npm install failed. Check the package name and network connectivity."
-  exit 1
-fi
-```
-
-### uninstall
-
-```bash
-[ -z "$plugin_id" ] && { echo "ERROR: --plugin-id required."; exit 1; }
-
-exists=$(jq -r --arg id "$plugin_id" '[(.plugins // [])[] | select(.id == $id)] | length' "$registryFile")
-[ "$exists" -eq 0 ] && { echo "ERROR: Plugin '$plugin_id' not found."; exit 1; }
-
-# Two-step confirmation
-if [ "${confirm:-}" != "yes" ]; then
-  pkg=$(jq -r --arg id "$plugin_id" '(.plugins // [])[] | select(.id == $id) | .packageName // $id' "$registryFile")
-  echo "UNINSTALL CONFIRMATION REQUIRED"
-  echo "────────────────────────────────────────────────────────"
-  echo "  Plugin:  $plugin_id  ($pkg)"
-  echo "  This will remove the plugin and all its configuration."
-  echo ""
-  echo "  To confirm: --action uninstall --plugin-id $plugin_id --confirm yes"
-  exit 0
-fi
-
-pkg=$(jq -r --arg id "$plugin_id" '(.plugins // [])[] | select(.id == $id) | .packageName // ""' "$registryFile")
-
-# Remove from registry
-tmp="${registryFile}.tmp"
-jq --arg id "$plugin_id" \
-  '.plugins = [(.plugins // [])[] | select(.id != $id)]' \
-  "$registryFile" > "$tmp" && mv "$tmp" "$registryFile"
-
-echo "Plugin '$plugin_id' removed from registry."
-
-# Attempt npm uninstall if packageName known
-if [ -n "$pkg" ]; then
-  echo "  Running: npm uninstall $pkg"
-  npm uninstall "$pkg" 2>&1 | tail -3 || echo "  WARNING: npm uninstall had errors — registry entry removed anyway."
-fi
-```
-
-### enable
-
-```bash
-[ -z "$plugin_id" ] && { echo "ERROR: --plugin-id required."; exit 1; }
-
-exists=$(jq -r --arg id "$plugin_id" '[(.plugins // [])[] | select(.id == $id)] | length' "$registryFile")
-[ "$exists" -eq 0 ] && { echo "ERROR: Plugin '$plugin_id' not found."; exit 1; }
-
-tmp="${registryFile}.tmp"
-jq --arg id "$plugin_id" \
-  '.plugins = [(.plugins // [])[] | if .id == $id then .status = "installed" | .disabledAt = null else . end]' \
-  "$registryFile" > "$tmp" && mv "$tmp" "$registryFile"
-
-echo "Plugin '$plugin_id' ENABLED."
-```
-
-### disable
-
-```bash
-[ -z "$plugin_id" ] && { echo "ERROR: --plugin-id required."; exit 1; }
-
-exists=$(jq -r --arg id "$plugin_id" '[(.plugins // [])[] | select(.id == $id)] | length' "$registryFile")
-[ "$exists" -eq 0 ] && { echo "ERROR: Plugin '$plugin_id' not found."; exit 1; }
-
-ts=$(date -u +%Y-%m-%dT%H:%M:%SZ)
-tmp="${registryFile}.tmp"
-jq --arg id "$plugin_id" --arg ts "$ts" \
-  '.plugins = [(.plugins // [])[] | if .id == $id then .status = "disabled" | .disabledAt = $ts else . end]' \
-  "$registryFile" > "$tmp" && mv "$tmp" "$registryFile"
-
-echo "Plugin '$plugin_id' DISABLED — will not load on next startup."
-```
-
-### check-updates
-
-```bash
-echo "CHECKING PLUGIN UPDATES"
-echo "────────────────────────────────────────────────────────"
-
-count=$(jq '.plugins | length' "$registryFile")
-[ "$count" -eq 0 ] && { echo "  No plugins installed."; exit 0; }
-
-jq -r '(.plugins // [])[] | select(.packageName != null) |
-  [.id, .packageName, (.version // "unknown")] | @tsv' \
-  "$registryFile" | while IFS=$'\t' read -r id pkg ver; do
-  latest=$(curl -sf "https://registry.npmjs.org/${pkg}/latest" 2>/dev/null | jq -r '.version // "?"' 2>/dev/null || echo "?")
-  if [ "$latest" != "?" ] && [ "$latest" != "$ver" ]; then
-    echo "  [$id]  $ver  →  $latest  — run: npm install $pkg"
-  else
-    echo "  [$id]  $ver  (up to date)"
-  fi
-done
-```
-
----
-
-## Step 3 — Return Output
-
-```yaml
-domain: ops
-status: complete
-action: <action>
-plugin_id: <plugin_id>
-```
-
----
-
-## Step 4 — Brain Write (standalone only)
-
-If `caller` is not "command", follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.