Help: what MasterMind can do, and how to use it

Present this as a clear, friendly menu (adapt length to the ask). Open with the brand header, then lead with the one thing that matters most, then the tables. Keep it scannable. Header:

🧠  MasterMind: a genius-builder brain for your AI
    33 skills · 4 agents · Claude Code · Cursor · Codex

Lead with what fits this project

Before the full menu, name up to three skills that would earn their keep here right now, each with the reason it applies: read from what's actually in front of you (the stack, the current task, what the last few turns were about, whether a field pack exists yet):

Most useful here right now
  · init: no field pack yet for this Django project; one-time setup, then I'm sharper on it
  · quarantine: there's client data in this repo; this keeps it out of git
  · handoff: this session is long; a handoff survives the reset

A full menu is a catalogue; three fitting picks are advice. Then give the tables below: the catalogue still matters, because the point is that the user learns what they already own.

The one rule: you don't run commands: you just talk

MasterMind works by recognizing intent. Say what you want in plain language and it applies the right skill or agent itself, then shows a short note that it did (e.g. 🧠 MasterMind ▸ building this, will verify before handoff, with └ build · design → implement → verify beneath it). The /name calls below are an optional shortcut: a way to force a specific skill, not something you need to memorize. Every skill is Auto (the model can invoke it); you can also call any of them by hand.

Skills: the workflows (all Auto-invocable)

Agents: the deep expert roles (isolated context)

Agents run in their own context for a focused job. MasterMind delegates to them inside a task; you can also summon one directly.

Skills vs agents (one line)

Skills are inline workflows that run in the current conversation; agents are separate expert roles with their own fresh context for a heavier, focused job. You rarely pick. MasterMind reaches for the right one and tells you.

Getting set up

If MasterMind isn't set up for this project yet (no field pack for your stack), it will offer a one-time setup, say "init" or just start working and it'll ask. Verify your install anytime with ~/.mastermind/install.sh --check.

Optional preferences (per project, kept in .mastermind/prefs.md; the first two are off by default):

• cycle report: a written write-up at the end of a build/QA cycle. Turn on: "reports on".
• plan-first: on bigger tasks, MasterMind shows the plan and waits for your OK before editing. Turn on: "plan first from now on".
• specs-dir: where spec-driven documents live, specs unless that folder already holds something else.

The first two behave exactly as their implementations define them, skills/build/SKILL.md (plan-first gate) and skills/report/SKILL.md (report formats).