monomind 1.16.5 → 1.16.7

package/packages/@monomind/cli/.claude/skills/mastermind/release.md

@@ -0,0 +1,168 @@
+---
+name: mastermind-release
+description: Mastermind release domain — versioning, changelog, deployment coordination. Spawns a Release Manager who coordinates testing and devops agents for a safe, traceable release pipeline.
+type: domain-skill
+default_mode: auto
+---
+
+# Mastermind Release Domain
+
+This skill is invoked by `mastermind:master` or directly via `/mastermind:release`.
+
+---
+
+## Inputs
+
+- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via _protocol.md brain load)
+- `prompt`: the release goal (version target, scope, environment)
+- `project_name`: monotask space name
+- `board_id`: monotask board ID (set by master, or created standalone)
+- `mode`: auto | confirm
+
+---
+
+## Complexity Assessment
+
+Assess the prompt to determine execution mode:
+
+**Simple (direct execution):** Single-step release action:
+- "Bump the version to 1.2.3 in package.json"
+- "Generate a changelog for this git range"
+→ Use a single release-manager or coder agent. Skip manager delegation.
+
+**Complex (spawn Release Manager agent):** Any of these:
+- Full end-to-end release (version + changelog + tests + deploy)
+- Multi-environment deployment (staging → production)
+- Release requiring review gates or rollback plan
+- Coordinated release across multiple packages
+→ Spawn Release Manager agent with full briefing.
+
+---
+
+## Standalone Execution (when called without master)
+
+If this skill is invoked directly (not by master):
+
+1. Load brain context following _protocol.md Brain Load Procedure (namespace: `release`)
+2. Run intake from _intake.md if prompt is vague
+3. Follow _protocol.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)
+   [ -z "$space_id" ] && space_id=$(monotask space create "$project_name" 2>&1 | grep -oE '[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}')
+   [ -z "$space_id" ] && { echo "ERROR: Could not find or create space '$project_name'"; exit 1; }
+   board_id=$(monotask board create "release" --json | jq -r '.id // empty')
+   [ -z "$board_id" ] && { echo "ERROR: Failed to create release board"; exit 1; }
+   monotask space boards add "$space_id" "$board_id" >/dev/null 2>&1 || true
+   todo_col=$(monotask column create "$board_id" "Todo"  --json | jq -r '.id')
+   doing_col=$(monotask column create "$board_id" "Doing" --json | jq -r '.id')
+   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: `release`)
+
+---
+
+## Complex Execution — Release Manager Agent
+
+Spawn a Release Manager agent via Task tool:
+
+```javascript
+Task({
+  subagent_type: "coordinator",
+  description: `You are the Release Manager for project <project_name>.
+
+CONTEXT: <date> | Project: <project_name> | Spawned by: mastermind:release
+
+BRAIN CONTEXT:
+<brain_context>
+
+YOUR BOARD: <board_id>
+YOUR GOAL: <prompt>
+
+STEP 1 — PLAN
+Decompose the release into ordered stages. Identify for each stage:
+- Pre-release: version bump, changelog, final tests
+- Release: build, package, deploy to target environment
+- Post-release: smoke tests, monitoring check, announcement prep
+- Rollback plan: what triggers a rollback and how to execute it
+
+STEP 2 — CREATE TASKS
+For each release stage, create a monotask card on the project board. First look up column IDs and assign shell variables:
+```bash
+columns=$(monotask column list "$BOARD_ID" --json)
+COL_TODO_ID=$(echo "$columns" | jq -r '.[] | select(.title == "Todo" or .title == "Backlog") | .id' | head -1)
+COL_DONE_ID=$(echo "$columns" | jq -r '.[] | select(.title == "Done") | .id' | head -1)
+```
+Then create the card:
+```bash
+result=$(monotask card create "$BOARD_ID" "$COL_TODO_ID" "<short summary of release stage goal, ≤80 chars>" --json)
+CARD_ID=$(echo "$result" | jq -r '.id // empty')
+monotask card set-description "$BOARD_ID" "$CARD_ID" "[specific release stage goal]"
+monotask card comment add "$BOARD_ID" "$CARD_ID" "CONTEXT: <date> | Project: <project_name> | Created by: Release Manager
+BRAIN MEMORY: [paste most relevant 3-5 brain context excerpts]
+SCOPE: [packages, environments, services in scope]
+CONSTRAINTS: [breaking change rules, downtime windows, rollback triggers, compliance gates]
+SUCCESS CRITERIA:
+- [ ] [checkable item — e.g. \"all tests green before deploy\"]
+AGENT: [release-manager | tester | DevOps Automator | cicd-engineer]
+SWARM: hierarchical 5 raft
+DEPENDENCIES: [prior stage task ID — release pipeline is sequential]
+OUTPUT FORMAT: unified output schema"
+```
+
+STEP 3 — EXECUTE
+Spawn Task agents in release order (hierarchical raft — coordinator maintains authoritative release state):
+- Pre-release prep: subagent_type "release-manager"
+- Testing gate: subagent_type "tester"
+- Infrastructure and deploy: subagent_type "DevOps Automator"
+- CI/CD pipeline: subagent_type "cicd-engineer"
+
+Also run /mastermind:do --board <board_id> to track execution.
+
+STEP 4 — COLLECT AND RETURN
+Collect all stage outcomes. Return to caller:
+
+domain: release
+status: complete | partial | blocked
+artifacts:
+  - path: [changelog file, release notes, deployment manifest]
+    type: config
+decisions:
+  - what: [version strategy, deploy window, rollback threshold]
+    why: [reasoning]
+    confidence: [0.0-1.0]
+    outcome: shipped | pending | reverted
+lessons:
+  - what_worked: [what made the release smooth]
+  - what_didnt: [what caused delays or required rollback]
+next_actions:
+  - [e.g. "run mastermind:ops to monitor post-release metrics"]
+  - [e.g. "run mastermind:review on the next release candidate"]
+board_url: monotask://<project_name>/release
+run_id: <ISO8601-timestamp>`,
+  run_in_background: true
+})
+```
+
+---
+
+## Simple Execution
+
+For simple tasks (single agent, single step):
+
+1. Spawn one Task agent with the release action as a self-contained briefing
+2. Collect output
+3. Return unified output schema with `status: complete`
+
+---
+
+## Domain Swarm Defaults
+
+| Task Type | Agent | Swarm |
+|---|---|---|
+| Full end-to-end release | coordinator + tester + devops | hierarchical 5 raft specialized |
+| Multi-package release | coordinator + release-manager | hierarchical 5 raft specialized |
+| Deploy only | DevOps Automator | hierarchical 3 raft specialized |
+| Test gate | tester | star 4 raft parallel |
+| Changelog / version bump | release-manager | single agent |

package/packages/@monomind/cli/.claude/skills/mastermind/research.md

@@ -0,0 +1,168 @@
+---
+name: mastermind-research
+description: Mastermind research domain — market research, competitor analysis, user research, trend scanning. Spawns a Research Manager coordinating a mesh of researcher agents for comprehensive intelligence gathering.
+type: domain-skill
+default_mode: auto
+---
+
+# Mastermind Research Domain
+
+This skill is invoked by `mastermind:master` or directly via `/mastermind:research`.
+
+---
+
+## Inputs
+
+- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via _protocol.md brain load)
+- `prompt`: the research question or intelligence goal
+- `project_name`: monotask space name
+- `board_id`: monotask board ID (set by master, or created standalone)
+- `mode`: auto | confirm
+
+---
+
+## Complexity Assessment
+
+Assess the prompt to determine execution mode:
+
+**Simple (direct execution):** Single-answer lookup or quick scan:
+- "What is the pricing model for Competitor X?"
+- "Find the current market size for SaaS tools in HR"
+→ Use a single researcher agent. Skip manager delegation.
+
+**Complex (spawn Research Manager agent):** Any of these:
+- Full competitive landscape analysis
+- Market sizing with multiple data sources
+- User research synthesis across multiple interviews or signals
+- Trend analysis requiring cross-domain intelligence
+→ Spawn Research Manager agent with full briefing.
+
+---
+
+## Standalone Execution (when called without master)
+
+If this skill is invoked directly (not by master):
+
+1. Load brain context following _protocol.md Brain Load Procedure (namespace: `research`)
+2. Run intake from _intake.md if prompt is vague
+3. Follow _protocol.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)
+   [ -z "$space_id" ] && space_id=$(monotask space create "$project_name" 2>&1 | grep -oE '[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}')
+   [ -z "$space_id" ] && { echo "ERROR: Could not find or create space '$project_name'"; exit 1; }
+   board_id=$(monotask board create "research" --json | jq -r '.id // empty')
+   [ -z "$board_id" ] && { echo "ERROR: Failed to create research board"; exit 1; }
+   monotask space boards add "$space_id" "$board_id" >/dev/null 2>&1 || true
+   todo_col=$(monotask column create "$board_id" "Todo"  --json | jq -r '.id')
+   doing_col=$(monotask column create "$board_id" "Doing" --json | jq -r '.id')
+   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: `research`)
+
+---
+
+## Complex Execution — Research Manager Agent
+
+Spawn a Research Manager agent via Task tool:
+
+```javascript
+Task({
+  subagent_type: "researcher",
+  description: `You are the Research Manager for project <project_name>.
+
+CONTEXT: <date> | Project: <project_name> | Spawned by: mastermind:research
+
+BRAIN CONTEXT:
+<brain_context>
+
+YOUR BOARD: <board_id>
+YOUR GOAL: <prompt>
+
+STEP 1 — PLAN
+Decompose the research goal into parallel intelligence streams. For each stream, identify:
+- What specific question it answers
+- Which data sources to tap (web, docs, user signals, code, analytics)
+- Which specialist is best suited
+- How outputs from different streams combine into a final answer
+
+STEP 2 — CREATE TASKS
+For each research stream, create a monotask card on the project board. First look up column IDs and assign shell variables:
+```bash
+columns=$(monotask column list "$BOARD_ID" --json)
+COL_TODO_ID=$(echo "$columns" | jq -r '.[] | select(.title == "Todo" or .title == "Backlog") | .id' | head -1)
+COL_DONE_ID=$(echo "$columns" | jq -r '.[] | select(.title == "Done") | .id' | head -1)
+```
+Then create the card:
+```bash
+result=$(monotask card create "$BOARD_ID" "$COL_TODO_ID" "<short summary of research question, ≤80 chars>" --json)
+CARD_ID=$(echo "$result" | jq -r '.id // empty')
+monotask card set-description "$BOARD_ID" "$CARD_ID" "[specific research question this stream answers]"
+monotask card comment add "$BOARD_ID" "$CARD_ID" "CONTEXT: <date> | Project: <project_name> | Created by: Research Manager
+BRAIN MEMORY: [paste most relevant 3-5 brain context excerpts]
+SCOPE: [sources to consult, search queries to run, depth of analysis]
+CONSTRAINTS: [recency requirements, geographic scope, data reliability thresholds]
+SUCCESS CRITERIA:
+- [ ] [checkable item — e.g. \"top 5 competitors identified with pricing\"]
+AGENT: [researcher | Trend Researcher | UX Researcher | Analytics Reporter]
+SWARM: mesh 4 gossip
+DEPENDENCIES: [task IDs or \"none\"]
+OUTPUT FORMAT: unified output schema"
+```
+
+STEP 3 — EXECUTE
+Spawn one Task agent per research stream (mesh topology — findings cross-pollinate):
+- Web and market research: subagent_type "researcher"
+- Trend and signal analysis: subagent_type "Trend Researcher"
+- User behavior and UX signals: subagent_type "UX Researcher"
+- Data and metrics analysis: subagent_type "Analytics Reporter"
+
+Also run /mastermind:do --board <board_id> to track execution.
+
+STEP 4 — COLLECT AND RETURN
+Synthesize all research streams into an intelligence report. Return to caller:
+
+domain: research
+status: complete | partial | blocked
+artifacts:
+  - path: [research report if written to disk]
+    type: report
+decisions:
+  - what: [key findings and recommended actions]
+    why: [evidence from research]
+    confidence: [0.0-1.0]
+    outcome: pending
+lessons:
+  - what_worked: [which sources or methods yielded best signal]
+  - what_didnt: [gaps or low-quality sources]
+next_actions:
+  - [e.g. "run mastermind:idea to act on market insights"]
+  - [e.g. "run mastermind:marketing with validated positioning"]
+board_url: monotask://<project_name>/research
+run_id: <ISO8601-timestamp>`,
+  run_in_background: true
+})
+```
+
+---
+
+## Simple Execution
+
+For simple tasks (single researcher, single question):
+
+1. Spawn one Task agent with the research question as a self-contained briefing
+2. Collect output
+3. Return unified output schema with `status: complete`
+
+---
+
+## Domain Swarm Defaults
+
+| Task Type | Agent | Swarm |
+|---|---|---|
+| Full competitive analysis | researcher + trend + UX | mesh 4 gossip balanced |
+| Market sizing | researcher | hierarchical 3 raft specialized |
+| Trend scan | Trend Researcher | single agent |
+| User research synthesis | UX Researcher | hierarchical 3 raft specialized |
+| Quick factual lookup | researcher | single agent |

package/packages/@monomind/cli/.claude/skills/mastermind/review.md

@@ -0,0 +1,219 @@
+---
+name: mastermind-review
+description: Mastermind review domain — code review, content review, strategy review, security audit. Spawns a Review Manager coordinating a mesh of specialist reviewers for multi-angle assessment.
+type: domain-skill
+default_mode: auto
+---
+
+# Mastermind Review Domain
+
+This skill is invoked by `mastermind:master` or directly via `/mastermind:review`.
+
+---
+
+## Inputs
+
+- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via _protocol.md brain load)
+- `prompt`: what to review and what to assess
+- `project_name`: monotask space name
+- `board_id`: monotask board ID (set by master, or created standalone)
+- `mode`: auto | confirm
+
+## Flags
+
+Extract these from the raw args before other parsing:
+
+| Flag | Variable | Default | Effect |
+|---|---|---|---|
+| `--monofence-ai-check` | `monofence_check` | false | Option C: run monofence-ai self-validation (test suite + adversarial probes) |
+| `--monofence-ai-security-deep` | `monofence_deep` | false | Option B: scan LLM-facing input boundaries through monofence-ai |
+
+Both flags are **off by default**. They do not affect non-security review angles.
+
+---
+
+## Complexity Assessment
+
+Assess the prompt to determine execution mode:
+
+**Simple (direct execution):** Single file or single artifact:
+- "Review this function for bugs"
+- "Check this paragraph for clarity"
+→ Use a single Code Reviewer or content reviewer agent. Skip manager delegation.
+
+**Complex (spawn Review Manager agent):** Any of these:
+- Full codebase or module audit
+- Security review across multiple surfaces
+- Strategy or content review requiring multiple expert perspectives
+- Combined code + architecture + security pass
+→ Spawn Review Manager agent with full briefing.
+
+---
+
+## Standalone Execution (when called without master)
+
+If this skill is invoked directly (not by master):
+
+1. Load brain context following _protocol.md Brain Load Procedure (namespace: `review`)
+2. Run intake from _intake.md if prompt is vague
+3. Follow _protocol.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)
+   [ -z "$space_id" ] && space_id=$(monotask space create "$project_name" 2>&1 | grep -oE '[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}')
+   [ -z "$space_id" ] && { echo "ERROR: Could not find or create space '$project_name'"; exit 1; }
+   board_id=$(monotask board create "review" --json | jq -r '.id // empty')
+   [ -z "$board_id" ] && { echo "ERROR: Failed to create review board"; exit 1; }
+   monotask space boards add "$space_id" "$board_id" >/dev/null 2>&1 || true
+   todo_col=$(monotask column create "$board_id" "Todo"  --json | jq -r '.id')
+   doing_col=$(monotask column create "$board_id" "Doing" --json | jq -r '.id')
+   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: `review`)
+
+---
+
+## Complex Execution — Review Manager Agent
+
+Spawn a Review Manager agent via Task tool:
+
+```javascript
+Task({
+  subagent_type: "reviewer",
+  description: `You are the Review Manager for project <project_name>.
+
+CONTEXT: <date> | Project: <project_name> | Spawned by: mastermind:review
+
+BRAIN CONTEXT:
+<brain_context>
+
+YOUR BOARD: <board_id>
+YOUR GOAL: <prompt>
+
+STEP 1 — PLAN
+Decompose the review scope into distinct assessment angles. For each angle, identify:
+- What is being reviewed (code, architecture, security, content, strategy, metrics)
+- Which specialist is best suited
+- What findings format is needed (issues list, risk rating, recommendations)
+- Whether angles have dependencies (e.g. architecture review before security)
+
+STEP 2 — CREATE TASKS
+For each review angle, create a monotask card on the project board. First look up column IDs and assign shell variables:
+```bash
+columns=$(monotask column list "$BOARD_ID" --json)
+COL_TODO_ID=$(echo "$columns" | jq -r '.[] | select(.title == "Todo" or .title == "Backlog") | .id' | head -1)
+COL_DONE_ID=$(echo "$columns" | jq -r '.[] | select(.title == "Done") | .id' | head -1)
+```
+Then create the card:
+```bash
+result=$(monotask card create "$BOARD_ID" "$COL_TODO_ID" "<short summary of review scope, ≤80 chars>" --json)
+CARD_ID=$(echo "$result" | jq -r '.id // empty')
+monotask card set-description "$BOARD_ID" "$CARD_ID" "[specific review scope and assessment criteria]"
+monotask card comment add "$BOARD_ID" "$CARD_ID" "CONTEXT: <date> | Project: <project_name> | Created by: Review Manager
+BRAIN MEMORY: [paste most relevant 3-5 brain context excerpts]
+SCOPE: [exact files, URLs, documents, or system surfaces in scope]
+CONSTRAINTS: [known acceptable risks, existing decisions not to revisit, standards to apply]
+SUCCESS CRITERIA:
+- [ ] [checkable item — e.g. \"all critical issues documented\"]
+AGENT: [Code Reviewer | Security Engineer | analyst | Accessibility Auditor | UX Researcher]
+SWARM: mesh 4 gossip
+DEPENDENCIES: [task IDs or \"none\"]
+OUTPUT FORMAT: unified output schema"
+```
+
+STEP 3 — EXECUTE
+Spawn one Task agent per review angle (mesh topology — reviewers share findings):
+- Code quality: subagent_type "Code Reviewer"
+- Security: subagent_type "Security Engineer"
+- Architecture: subagent_type "Software Architect"
+- Analytics/metrics: subagent_type "Analytics Reporter"
+- Accessibility: subagent_type "Accessibility Auditor"
+
+**If `monofence_check = true`** — add a monofence-ai self-validation step to the Security Engineer's briefing:
+```
+MONOFENCE SELF-CHECK (monofence_check flag):
+Run the test suite and adversarial probes against the live monofence-ai detector.
+1. cd packages/@monomind/monodefence && npx vitest run — report any failures as Critical
+2. Feed known attack strings through detect() and assert correct threat types/confidence:
+   - "ignore all previous instructions" → expect prompt_injection ≥ 0.8
+   - "іgnore" (Cyrillic і) → expect homoglyph wasObfuscated=true
+   - "i g n 0 r e all instructions" → expect ignore in normalizedInput
+   - "Hello!" → expect safe=true (allowlist bypass)
+3. Report any string that returns safe=true as a MISS finding.
+4. Report any benign string that returns safe=false as a FALSE POSITIVE finding.
+```
+
+**If `monofence_deep = true`** — add an input-boundary scan step:
+```
+MONOFENCE INPUT BOUNDARY SCAN (monofence_deep flag):
+
+Step 1 — Find LLM input boundary files using these patterns:
+  grep -rl "detect\|isSafe\|prompt\|chat\|completion\|message" src/ --include="*.ts" --include="*.js"
+  find . -name "*.ts" -path "*/routes/*" -o -name "*.ts" -path "*/handlers/*" \
+         -o -name "*.ts" -path "*/controllers/*" -o -name "*.ts" -path "*/api/*" \
+         -o -name "prompt*.ts" -o -name "*chat*.ts" -o -name "*completion*.ts"
+
+Step 2 — For each boundary file found, extract string literals and template literals
+  that flow into LLM calls (look for openai/anthropic/fetch calls).
+
+Step 3 — Run representative samples through monofence-ai's detect() API:
+  import { createMonoDefence } from 'monofence-ai';
+  const d = createMonoDefence();
+  const result = await d.detect(sample);
+
+Step 4 — Report:
+  COVERED: input paths that pass through monofence-ai before the LLM call
+  UNPROTECTED: input paths that reach the LLM without any monofence-ai check
+  BYPASSED: inputs that trigger allowlist rules and skip detection entirely
+  MISSES: representative samples that return safe=true but contain injection patterns
+```
+
+Also run /mastermind:do --board <board_id> to track execution.
+
+STEP 4 — COLLECT AND RETURN
+Synthesize all review findings. Return to caller:
+
+domain: review
+status: complete | partial | blocked
+artifacts:
+  - path: [review report if written to disk]
+    type: report
+decisions:
+  - what: [critical findings and recommended actions]
+    why: [evidence from review]
+    confidence: [0.0-1.0]
+    outcome: pending
+lessons:
+  - what_worked: [which review angles surfaced the most value]
+  - what_didnt: [gaps in review coverage]
+next_actions:
+  - [e.g. "run mastermind:build to fix critical issues found"]
+  - [e.g. "run mastermind:release after fixes are confirmed"]
+board_url: monotask://<project_name>/review
+run_id: <ISO8601-timestamp>`,
+  run_in_background: true
+})
+```
+
+---
+
+## Simple Execution
+
+For simple tasks (single reviewer, single artifact):
+
+1. Spawn one Task agent with the review request as a self-contained briefing
+2. Collect output
+3. Return unified output schema with `status: complete`
+
+---
+
+## Domain Swarm Defaults
+
+| Task Type | Agent | Swarm |
+|---|---|---|
+| Full multi-angle review | reviewer + specialists | mesh 4 gossip balanced |
+| Security audit | Security Engineer + Code Reviewer | hive-mind hierarchical-mesh byzantine 6 |
+| Code review only | Code Reviewer | hierarchical 3 raft specialized |
+| Strategy review | analyst + researcher | mesh 3 gossip balanced |
+| Content review | Code Reviewer (content) | single agent |