**First — extract repeat flags:** Follow the REPEAT PREAMBLE from `mastermind-repeat/SKILL.md`. Extracts `--repeat`, `--tillend`, `--maxruns`, `--wait`, `--rep`, `--loop` from `$ARGUMENTS` before all other parsing. If `is_continuation = true`, skip the empty-arguments check below. If `$ARGUMENTS` is empty, output this and STOP: > **Usage:** `/mastermind:ideate ` > > Example: `/mastermind:ideate add real-time collaboration to the editor` > > By default, ideas are saved to `docs/ideas/YYYY-MM-DD-.md`. Add `--monotask` to write to a monotask board instead. Do NOT proceed further if no arguments were provided. **Extract `--monotask` flag:** If present, set `USE_MONOTASK=true` and remove from `$ARGUMENTS`. Default: `USE_MONOTASK=false`. --- ## Step 0: Check 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: Gather Project Context Collect ALL of the following in parallel (skip any that error): 1. **Repo name**: Run `git remote get-url origin`, extract the last path segment, strip `.git`. Fallback: `basename` of the current working directory. Store as `REPO_NAME`. 2. **README**: Read `README.md` (first 200 lines). Skip if missing. 3. **Package manifest**: Read whichever exists first: `package.json`, `Cargo.toml`, `pyproject.toml`, `go.mod`. Extract name, description, and keywords/tags. 4. **Knowledge graph**: Call `mcp__monomind__monograph_suggest` with the user's prompt (`$ARGUMENTS`). Skip if it errors or returns empty. 5. **Memory search**: Call `mcp__monomind__memory_pattern-search` with the user's prompt (`$ARGUMENTS`). Use the top 5 results. Bundle all gathered information into a single `PROJECT_CONTEXT` string for downstream agents. --- ## Step 2: Setup Storage **File mode (default):** ```bash DATE=$(date +%Y-%m-%d) SLUG=$(echo "$ARGUMENTS" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g; s/-\+/-/g; s/^-//; s/-$//' | cut -c1-40) IDEA_FILE="docs/ideas/${DATE}-${SLUG}.md" mkdir -p docs/ideas ``` Write the file header using the Write tool: ```markdown --- source: mastermind:ideate repo: created: prompt: --- # Ideas: <$ARGUMENTS> ``` Store `IDEA_FILE`. --- **Monotask mode:** - Find or create space `$REPO_NAME` → store `SPACE_ID` - Find or create `monomind-idea` board with columns: `New`, `Evaluated`, `Elaborated`, `Tasked`, `Iced`, `Rejected` → store `BOARD_ID` and all column IDs --- ## Step 3: Research Swarm -- Generate Ideas Spawn 3-5 `researcher` agents in parallel using the Agent tool (mesh topology). Each agent receives: - The user's prompt: `$ARGUMENTS` - The `PROJECT_CONTEXT` string from Step 1 Each agent should generate ideas as a JSON array. There is no hard cap — generate as many or as few as the topic warrants. Ideas should span **two categories**: 1. **Feature/capability ideas** — what to build, what problem it solves, why it matters. 2. **Technical stack & baseline decisions** — foundational choices that must be made before implementation (e.g., "Use PostgreSQL vs SQLite for persistence", "Adopt event-driven architecture vs request-response", "Choose WebSocket vs SSE for real-time updates", "Define the API versioning strategy"). These are the "how" decisions that shape everything downstream. ```json [ { "title": "Short idea title", "description": "2-3 sentence description of the idea, what it solves, and why it matters.", "category": "feature | technical-baseline" } ] ``` After all agents complete: 1. Merge all idea arrays. 2. Deduplicate by title similarity (fuzzy match — drop ideas whose titles are >80% similar to an already-kept idea). 3. Persist each unique idea: **File mode:** Append to `IDEA_FILE` using the idea section format from `mastermind-taskfile/SKILL.md`: ```markdown ### > status: new > category: --- ``` **Monotask mode:** ```bash monotask card create $BOARD_ID $COL_NEW "