Mind Map Diagram Generator

Quick Start: Start with @startmindmap -> define root and branches with * or +/- markers -> optionally set branch side, direction, and styles -> wrap in ```plantuml fence.

⚠️ IMPORTANT: Always use ```plantuml or ```puml code fence. NEVER use ```text — it will NOT render as a diagram.

When To Use / Diagnostic Intake

适用于层级分解和头脑风暴整理。先确定根主题、深度、原始清单、左右布局以及必须保留的节点；流程时序不宜隐含在树中。

Workflow

确定一个根→去除无依据节点→整理父子层级→设置方向和必要样式→生成 PlantUML→检查闭合及渲染结果。

Tools and Dependencies

需要支持 @startmindmap 的 PlantUML；不可用时交付可复制源文件和未渲染说明。

Critical Rules

• Every diagram starts with @startmindmap and ends with @endmindmap
• Each hierarchy level is represented by repeating markers:
  • * style: * (root), ** (level 1), *** (level 2)
  • +/- style: + grows left branch, - grows right branch
• Keep one marker style consistent in the same local branch (do not randomly mix indentation styles)
• Use left side to switch subsequent branches to the left side of the root
• Use direction keywords when needed:
  • top to bottom direction
  • right to left direction
• Multi-line node content must use block syntax:
  • **:Line 1\nLine 2;
• For quick color coding, use inline node color:
  • *[#Orange] Root
  • **[#lightgreen] Child
• For reusable themes, define <style> and apply stereotypes like <<green>>
• Rich text/Creole and icon syntax are supported inside node text (see examples)

Node Syntax Cheat Sheet

Branch Side and Direction

Styling Options

Recommended Color Palettes

Pick a palette that matches the map's purpose. Use inline [#hex] for quick coloring or define <style> classes for reuse.

General-Purpose (Pastel)

Status / RAG

Warm Corporate

Cool Tech

Earth Tone

Tip: Avoid pure saturated colors (#FF0000, #00FF00) — they reduce readability. Prefer soft/muted tones for backgrounds and reserve bold colors for the root only.

Mind Map Patterns

Quick Example

@startmindmap
* Product Launch
** Goals
*** Revenue
*** User Growth

left side
** Risks
*** Timeline Slip
*** Budget Overrun

right to left direction
** Channels
*** Content
*** Ads
@endmindmap

Common Pitfalls

Capability Upgrade

Mode Selection

• Quick: 把主题拆成 2-3 层思维导图。
• Standard: 形成结构清晰、左右平衡、带颜色层级的 PlantUML mindmap。
• Deep: 结合项目目标、知识库内容、会议记录或战略框架，生成可用于研讨、培训或汇报的结构化导图。

Structure Logic

先确定导图目的：发散、归纳、决策、学习、路线图或问题拆解。目的不同，分支应分别按 MECE、时间、责任、因果或优先级组织。

Quality Gates

• 一级分支 3-7 个，避免过宽或过窄。
• 同层节点使用同一分类口径。
• 分支深度不超过可读范围。
• 颜色用于表达语义，不只是装饰。
• 输出包含 PlantUML 和必要的结构解释。

Deliverable Catalog

Delivery Verification Materials

• 场景与预期交付：合成案例及缺失输入、注入指令变体。
• 逐项验收依据：本能力特有的检查项与复核记录。