If `$ARGUMENTS` is empty, output this and STOP: > **Usage:** `/mastermind:createtask ` > > 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-.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: ---` 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_pattern-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 --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: created: prompt: recommended_mode: --- # Tasks: --- ``` 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: