Mindmap Builder

---
name: mindmap-builder
description: Use when generating a Mermaid mindmap for brainstorming, topic exploration, or breaking down a problem. Triggers on "mindmap", "brainstorm diagram", "topic map", "break this down into branches".
---

# Mindmap Builder

Generate a Mermaid `mindmap` to externalize messy thinking. Mindmaps are exploratory — they're for the moment when "I have a topic and 14 thoughts" needs to become "I have a topic and 4 themes." Don't overengineer.

## Required inputs

1. **The central topic** — one phrase, ~5 words max
2. **The branches you already know** — even a few. If the user hasn't started, ask what 3-4 themes feel obvious.
3. **The depth target** — usually 2 levels (branch + sub-branch). 3 max. More than that and the mindmap becomes a tree.
4. **The intended use** — planning doc, retro, kickoff slide. Mindmaps for slides should be tighter than mindmaps for personal use.

If the user gives you 50 raw bullets and says "make a mindmap," push back: "Let's group these first. What are the 4-6 themes you see across the bullets?" The grouping is the value; the diagram is the artifact.

## Mermaid syntax to use

`mindmap` syntax is indentation-based. The root node uses double parens `((...))` for a circle, `[...]` for a rounded rectangle, `)...(` for a cloud, etc. Child nodes are just indented.

\`\`\`mermaid
mindmap
  root((Pricing page launch))
    Messaging
      Value prop
      Comparison vs competitors
      Pricing tier names
    Design
      Hero section
      Feature comparison table
      Mobile layout
    Engineering
      A/B test infrastructure
      CMS integration
      Analytics events
    Analytics
      Conversion tracking
      Funnel definition
      Dashboards
    Comms
      Customer email
      Internal announcement
      Sales enablement
\`\`\`

You can use icons via `::icon(fa fa-something)` if your renderer supports Font Awesome (Mermaid Live Editor does). Skip icons for serious work — they're decorative.

## Layout principles

- **Central topic in the middle**, primary branches radiating out. That's how Mermaid renders `mindmap` regardless of order.
- **3-7 primary branches.** Fewer feels thin; more becomes a list.
- **2 levels of depth.** Root → branch → sub-branch. If you need a third level, the topic might not be a mindmap candidate — it's a hierarchy.
- **Branch labels are nouns or noun phrases.** "Messaging," not "Decide on messaging."
- **Sub-branches under one parent should be parallel** — same level of abstraction, similar grain. "Hero section" and "Pick a font" don't belong as siblings.
- **Asymmetry is fine.** One branch with 5 sub-branches and another with 1 is honest — the tree should reflect where the work is.

## Anti-patterns

- **Mindmap as a deeply nested tree** — if you're 4 levels deep, you've drawn an org chart. Use a different tool.
- **Verbs on branches** — mindmaps are about *what*, not *do*. "Customer feedback" beats "Collect customer feedback."
- **One sub-branch per branch** — if a branch has only one child, just put it on the branch.
- **Mindmap shipped to execs** — they're working artifacts. For external docs, convert to a structured outline or a flowchart.
- **Decoration over signal** — colors, icons, and shapes should encode meaning or stay off.

## When to convert away from a mindmap

Once a mindmap has stabilized (after a session or two), promote it:
- To a **document outline** (flat headings)
- To a **decision tree** if the branches are conditional
- To a **work breakdown** with owners and dates
- To an **architecture diagram** if the branches turned out to be components

The mindmap was the scaffold; the structured doc is the building.

## Rendering hints

- GitHub renders Mermaid mindmaps (since v9.x). Confluence and Notion support varies — check your rendering before relying on it.
- Mermaid Live Editor handles mindmaps cleanly and exports to SVG/PNG.
- For slide decks, a mindmap rendered as an image is fine; for docs, prefer the live source.

## Output

The ```mermaid block plus 1 line: branch count and sub-branch count. If sub-branches are heavily skewed toward one branch, mention it — usually that's where the real work is, and worth flagging.