monomind 2.7.12 → 2.7.14

package/packages/@monomind/cli/.claude/commands/mastermind/createtask.md

@@ -1,372 +0,0 @@
-<!-- "Mastermind — Ingest a prompt, file, or folder, deeply understand it, generate agent-optimized tasks saved to docs/tasks/ (default) or to a monotask board (--monotask flag)" -->
-
-If `$ARGUMENTS` is empty, output this and STOP:
-
-> **Usage:** `/mastermind:createtask <prompt | path-to-file | path-to-folder>`
->
-> Examples:
-> - `/mastermind:createtask Build a webhook delivery system with retries and dead-letter queue`
-> - `/mastermind:createtask docs/superpowers/specs/2026-04-27-swarm-tab-redesign-design.md`
-> - `/mastermind:createtask docs/superpowers/specs/`
->
-> By default tasks are saved to `docs/tasks/YYYY-MM-DD-<slug>.md` — no external tools needed. Add `--monotask` to write to a monotask board instead.
-
-Do NOT proceed further if no arguments were provided.
-
-**Extract `--monotask` flag:** If `--monotask` is present anywhere in `$ARGUMENTS`, set `USE_MONOTASK=true` and remove it from `$ARGUMENTS`. Default: `USE_MONOTASK=false`.
-
----
-
-## Step 0: Verify monotask CLI *(skip unless `--monotask` was passed)*
-
-**Only run this step if `USE_MONOTASK=true`.**
-
-```bash
-command -v monotask || (command -v cargo && cargo install monotask)
-```
-If neither exists, tell user to install Rust + monotask and STOP.
-
----
-
-## Step 1: Classify and Ingest Input
-
-Parse `$ARGUMENTS`:
-- `test -f` → file: read with Read tool, store as `RAW_CONTENT`, store filename as `INPUT_LABEL`
-- `test -d` → folder: `find "$ARGUMENTS" -maxdepth 2 -type f ! -name '.*' | head -30`, read each, concatenate with `--- FILE: <path> ---` separators as `RAW_CONTENT`
-- Otherwise → prompt: store text directly as `RAW_CONTENT`
-
----
-
-## Step 2: Enrich with Project Context
-
-Run ALL in parallel (skip errors):
-1. `mcp__monomind__monograph_suggest` with first 200 chars of `RAW_CONTENT`
-2. `mcp__monomind__monograph_query` for module/component names found in `RAW_CONTENT` (up to 5)
-3. `mcp__monomind__memory_search` with input summary
-4. Read `README.md` (first 200 lines)
-5. Read first found: `package.json`, `Cargo.toml`, `pyproject.toml`, `go.mod`
-6. Repo name from `git remote get-url origin` (strip path, strip `.git`) — store as `REPO_NAME`
-
-Bundle everything into `FULL_CONTEXT`.
-
----
-
-## Step 3: Setup Storage
-
-**File mode (default, `USE_MONOTASK=false`):**
-
-Compute the output path (follow slug rules from `mastermind-taskfile/SKILL.md`):
-```bash
-DATE=$(date +%Y-%m-%d)
-SLUG=$(echo "$INPUT_LABEL" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g; s/-\+/-/g; s/^-//; s/-$//' | cut -c1-40)
-TASK_FILE="docs/tasks/${DATE}-${SLUG}.md"
-mkdir -p docs/tasks
-```
-
-Store `TASK_FILE`. You will write all tasks into this single file in Step 6.
-
----
-
-**Monotask mode (`USE_MONOTASK=true`):**
-
-**Space**: Find or create space named `$REPO_NAME`. Store `SPACE_ID`.
-
-**Board**: Retrieve stored board ID first: `npx monomind@latest memory search "monomind-task board_id"`. If found, use it as `TASK_BOARD_ID`. Otherwise, list boards in the space via `monotask space boards list $SPACE_ID` and check each via `monotask column list <ID> --json` for a `Backlog` column. If still not found, create:
-```bash
-monotask board create "monomind-task" --json   # captures TASK_BOARD_ID from .id
-monotask space boards add $SPACE_ID $TASK_BOARD_ID
-npx monomind@latest memory store --key "monomind-task board_id" --value "$TASK_BOARD_ID" --namespace monomind
-```
-Create columns in order: `Backlog` → `Todo` → `In Progress` → `Review` → `Human in Loop` → `Done`
-
-Store all column IDs mapped by name. Store `TASK_BOARD_ID`.
-
----
-
-## Step 4: Deep Analysis
-
-Spawn a `Software Architect` agent. Provide `FULL_CONTEXT` + `$ARGUMENTS`.
-
-Required output:
-```json
-{
-  "summary": "2-3 sentence overview",
-  "goals": ["high-level goals"],
-  "components": [
-    {
-      "name": "component name",
-      "description": "what it does",
-      "dependencies": ["other components"],
-      "files_likely_affected": ["paths from monograph or educated guesses"]
-    }
-  ],
-  "technical_constraints": ["stack requirements, limitations"],
-  "acceptance_criteria": ["testable conditions for when the whole thing is done"],
-  "risks": ["pitfalls, ambiguities, unknowns"]
-}
-```
-
-Store as `ANALYSIS`.
-
----
-
-## Step 5: Generate Professional Tasks
-
-Spawn a `planner` agent. Provide analysis + `FULL_CONTEXT`.
-
-### Task Grouping Rules (enforce all 7)
-
-1. **Context Affinity**: Work sharing the same files, types, or domain model goes in ONE task. Tests always travel with their implementation.
-2. **Size Limit**: If a context group exceeds 30 minutes, split into a prerequisite chain.
-3. **Independence**: Work touching different modules with no shared types should be separate (parallelizable).
-4. **Test Colocation**: Never create standalone "write tests" tasks — only exception is integration/e2e tests spanning multiple components.
-5. **Prerequisite Chains**: Use `prerequisites` to enforce ordering. Same agent picks up the chain in sequence.
-6. **Chain Size Limit**: Max 4 tasks per chain. Split larger chains into two sub-chains linked by prerequisite.
-7. **Agent Capability**: Agent type must match the domain (no frontend agent on DB migrations, no backend-dev on CSS).
-
-### Task Card Format
-
-For each task, produce:
-```json
-{
-  "title": "Action-oriented title (verb + noun + context)",
-  "description": "## What\nExact deliverable.\n\n## Why\nMotivation.\n\n## Where\nFile paths, module boundaries.\n\n## Patterns\nExisting conventions to follow.",
-  "context": "All relevant context: patterns, related files, API shapes, data models. Include file paths from monograph.",
-  "definition_of_done": ["Specific, binary, verifiable condition"],
-  "testing_criteria": {
-    "unit_tests": ["function(input) → expected outcome"],
-    "integration_tests": ["endpoint + method → status + response shape"],
-    "edge_cases": ["boundary condition → expected behavior"]
-  },
-  "checklist": [
-    "Write failing test for [specific behavior]",
-    "Implement [function/class] in [file path]",
-    "Run tests — verify green",
-    "Commit: '[type]: [description]'"
-  ],
-  "agent_type": "best-fit agent from 230+ roster",
-  "priority": "critical | high | medium | low",
-  "effort": "1-10",
-  "prerequisites": ["titles of tasks that MUST complete first"],
-  "parallel_safe": true,
-  "context_group": "name of context chain, or 'independent'"
-}
-```
-
-Store as `TASKS` array.
-
----
-
-## Step 6: Persist Tasks
-
-**File mode (default, `USE_MONOTASK=false`):**
-
-Write the file using the Write tool. Follow the task section format from `mastermind-taskfile/SKILL.md` exactly. The file structure:
-
-1. **Write frontmatter + header** (once):
-```markdown
----
-source: mastermind:createtask
-repo: <REPO_NAME>
-created: <DATE>
-prompt: <first 100 chars of $ARGUMENTS>
-recommended_mode: <parallel|minimal|sequential>
----
-
-# Tasks: <INPUT_LABEL>
-
-<ANALYSIS.summary>
-
----
-```
-
-2. **Append one section per task** (initial status = `todo` if no prerequisites, `backlog` if has prerequisites), following the task section format from `mastermind-taskfile/SKILL.md`:
-```markdown
-## Task N: <title>
-
-> status: todo
-> agent: <agent_type>
-> priority: <priority>
-> effort: <effort>
-> context_group: <context_group>
-> prerequisites: <none | comma-separated titles>
-> parallel_safe: <true|false>
-
-### What
-<description What section>
-
-### Why
-<description Why section>
-
-### Where
-<description Where section>
-
-### Context
-<context>
-
-### Definition of Done
-- [ ] <condition>
-
-### Testing Criteria
-- Unit: `<unit test>`
-- Integration: `<integration test>`
-- Edge case: `<edge case>`
-
-### Checklist
-- [ ] <step>
-- [ ] Run tests — verify green
-- [ ] Commit: '<type>: <description>'
-
----
-```
-
-Write all tasks in prerequisite order (prerequisites before dependents). Store `TASK_FILE` for use in Step 10.
-
----
-
-**Monotask mode (`USE_MONOTASK=true`):**
-
-For each task, in prerequisite order:
-
-1. **Create card** in `Todo` (no prerequisites) or `Backlog` (has prerequisites):
-   ```bash
-   monotask card create $TASK_BOARD_ID $COLUMN_ID "<title>" --json
-   ```
-
-2. **Set description**:
-   ```bash
-   monotask card set-description $TASK_BOARD_ID $CARD_ID "<description>\n\n## Context\n<context>\n\n## Context Group\n<context_group>"
-   ```
-
-3. **Add DOD comment**:
-   ```bash
-   monotask card comment add $TASK_BOARD_ID $CARD_ID "## Definition of Done\n- [ ] <condition 1>\n..."
-   ```
-
-4. **Add testing criteria comment**:
-   ```bash
-   monotask card comment add $TASK_BOARD_ID $CARD_ID "## Testing Criteria\n\n### Unit Tests\n- <test 1>\n\n### Integration Tests\n- <test 1>\n\n### Edge Cases\n- <case 1>"
-   ```
-
-5. **Add agent assignment + metadata**:
-   ```bash
-   monotask card comment add $TASK_BOARD_ID $CARD_ID "Assigned agent: <agent_type>\nContext group: <context_group>\nParallel safe: <true|false>\nPriority: <priority>\nEffort: <effort>/10\nPrerequisites: <task titles or none>\nSource: mastermind:createtask"
-   ```
-
-6. **Set priority**:
-   ```bash
-   PRIORITY="<current task's priority field — one of: critical, high, medium, low>"
-   case "$PRIORITY" in
-     critical) PNUM=1 ;; high) PNUM=2 ;; medium) PNUM=3 ;; *) PNUM=4 ;;
-   esac
-   monotask card set-priority $TASK_BOARD_ID $CARD_ID $PNUM
-   ```
-
-7. **Create checklist**:
-   ```bash
-   checklist_result=$(monotask checklist add $TASK_BOARD_ID $CARD_ID "Implementation Steps" --json)
-   CHECKLIST_ID=$(echo "$checklist_result" | jq -r '.id // empty')
-   ITEM_IDS=""
-   # For each checklist step <step>:
-   item_out=$(monotask checklist item-add $TASK_BOARD_ID $CARD_ID $CHECKLIST_ID "<step>")
-   ITEM_ID=$(echo "$item_out" | grep -oE '[0-9a-f-]{36}$')
-   ITEM_IDS="${ITEM_IDS:+$ITEM_IDS,}$ITEM_ID"
-   # After all items:
-   monotask card comment add $TASK_BOARD_ID $CARD_ID "CHECKLIST_ID: $CHECKLIST_ID"
-   monotask card comment add $TASK_BOARD_ID $CARD_ID "ITEM_IDS: $ITEM_IDS"
-   ```
-
----
-
-## Step 7: Store Session Memory
-
-**File mode (default):** The frontmatter in `TASK_FILE` already records `recommended_mode`. No additional storage needed.
-
-**Monotask mode:** Call `mcp__monomind__memory_store` with:
-```json
-{
-  "key": "task-strategy:<REPO_NAME>:<timestamp>",
-  "content": {
-    "source": "mastermind:createtask: <first 100 chars of $ARGUMENTS>",
-    "total_tasks": "N",
-    "context_groups": [
-      { "name": "group name", "task_titles": ["..."], "recommended_agent": "agent type", "sequential": true }
-    ],
-    "independent_tasks": ["titles of parallel-safe tasks"],
-    "recommended_execution_mode": "parallel | minimal | sequential",
-    "reasoning": "Why this mode fits"
-  },
-  "tags": ["task-strategy", "mastermind:createtask"]
-}
-```
-
-Mode selection: **parallel** = mostly independent tasks; **minimal** = mixed; **sequential** = heavy shared state.
-
----
-
-## Step 8: Final Dependency Review
-
-Spawn a fresh `Code Reviewer` agent. Provide the complete `TASKS` array and `REPO_NAME`.
-
-The agent MUST check:
-- **Prerequisite integrity**: all referenced prerequisites exist, no circular deps, no orphans
-- **Context group consistency**: compatible agent types per group, no group >4 tasks, tasks in group are chained
-- **Critical path**: identify longest chain, flag if >6 tasks or any single task >effort 7
-- **Parallel safety**: `parallel_safe: true` tasks don't share modified files
-- **Agent assignment**: no frontend agent on backend tasks, no agent in >5 context groups
-
-**If APPROVED**: present summary and proceed to execution offer.
-**If NEEDS_FIXES**: auto-fix blockers in the TASKS array (update prerequisite/group/agent fields in memory before writing), present warnings to user, max 2 fix cycles.
-
----
-
-## Step 9: Gap Analysis
-
-Spawn a fresh `Software Architect` agent as critical reviewer. Provide `ANALYSIS` + all created tasks.
-
-Identify:
-- **Missing pieces**: testing gaps, error handling holes, security oversights, missing migrations
-- **Follow-ups**: natural extensions, performance optimizations
-
-Present as tables. Ask user which to add (`numbers`, `all`, or `none`). Selected missing pieces → `todo` status (ready to execute); follow-ups → `backlog` status (deferred).
-
----
-
-## Step 10: Summary and Execution Offer
-
-**File mode (default):**
-```
-## Task Creation Complete
-
-**File:** <TASK_FILE>
-**Source:** <input>
-**Recommended mode:** <parallel|minimal|sequential>
-
-| # | Title | Agent | Priority | Effort | Status | Deps |
-|---|-------|-------|----------|--------|--------|------|
-| 1 | ...   | ...   | high     | 3      | todo   | —    |
-
-**Total:** N tasks saved to <TASK_FILE>
-```
-
-If there are todo tasks:
-> **N tasks ready.** Run `/mastermind:do --file <TASK_FILE>` to execute them, or `/mastermind:do --file <TASK_FILE> --mode parallel` to specify mode.
-
----
-
-**Monotask mode:**
-```
-## Task Creation Complete
-
-**Source:** <input>
-**Space:** $REPO_NAME | **Board:** monomind-task
-
-| # | Title | Agent | Priority | Effort | Column | Deps |
-|---|-------|-------|----------|--------|--------|------|
-| 1 | ...   | ...   | high     | 3      | Todo   | —    |
-
-**Total:** N tasks (X in Todo, Y in Backlog)
-```
-
-If there are tasks in Todo:
-> **N tasks ready.** Start `/mastermind:do --monotask --space $SPACE_ID --board $TASK_BOARD_ID` to execute them autonomously?

package/packages/@monomind/cli/.claude/commands/mastermind/debug.md

@@ -1,19 +0,0 @@
-<!-- Systematic root-cause debugging — use before ANY fix attempt for bugs, test failures, unexpected behavior, build failures, or performance regressions. Enforces Phase 1 root-cause investigation before proposing fixes. -->
-
-**First — extract repeat flags:** Follow the REPEAT PREAMBLE from `mastermind-repeat/SKILL.md`.
-
-Parse `$ARGUMENTS` for `--auto`, `--confirm`, `--project <name>`, and remaining text = problem description.
-
-Load brain context for the `debug` domain (follow `mastermind-protocol/SKILL.md` Brain Load Procedure).
-
-If problem description is empty: ask "What issue are you debugging?"
-
-Default mode: **auto** (proceed immediately; the skill gates on root-cause investigation, not on user confirmation).
-
----
-
-Invoke `Skill("mastermind-debug")` passing: brain_context, problem_description, mode.
-
-After skill returns: follow `mastermind-protocol/SKILL.md` Brain Write Procedure for domain `debug`.
-
-**MANDATORY — invoke `Skill("mastermind-repeat")` now.** This is required regardless of how the skill above completed, regardless of whether you think the work is done, regardless of whether you plan to end your response. For `--repeat N`: the count is non-negotiable — all N runs must happen. For `--tillend`: only a verified empty round (confirmed by git diff) stops the loop. Do not end your response without invoking this skill.

package/packages/@monomind/cli/.claude/commands/mastermind/design.md

@@ -1,17 +0,0 @@
-<!-- Collaborative design session — explore intent, clarify requirements, propose approaches, and produce an approved spec before any implementation begins. -->
-
-**First — extract repeat flags:** Follow REPEAT PREAMBLE from `mastermind-repeat/SKILL.md`.
-
-Parse `$ARGUMENTS` for `--auto`, `--confirm`, `--project <name>`, and remaining text.
-
-Load brain context (follow `mastermind-protocol/SKILL.md` Brain Load Procedure).
-
-Default mode: **confirm**.
-
----
-
-Invoke `Skill("mastermind-design")` passing: brain_context, params, mode.
-
-After skill returns: follow `mastermind-protocol/SKILL.md` Brain Write Procedure.
-
-Invoke `Skill("mastermind-repeat")` now. Required — do not skip.