Mermaid Diagrams
Create effective, syntactically valid mermaid diagrams for product documents.
When to Use
- Creating mermaid diagrams for PRDs, specs, roadmaps, or stakeholder presentations
- Choosing which of 15 diagram types fits a specific communication need
- Debugging mermaid code that won't render or renders incorrectly
- Reviewing diagrams for clarity, accuracy, and accessibility
When NOT to Use
- Exporting diagrams to image files (PNG/SVG) - that's a rendering tool concern
- Using non-mermaid diagramming tools (Figma, Lucidchart, draw.io)
- Creating purely decorative visuals with no informational purpose
- Producing a full customer-journey artifact (stages, touchpoints, emotional curve, pain points) rather than a standalone diagram - use
discover-journey-map, which composes this skill for its timeline or flowchart section
The Cardinal Rule
Don't diagram what a list can say.
Diagrams earn their place when they reveal relationships, branching, or flow that prose flattens. Before creating any diagram, ask:
Does this show branching, relationships, or flow that a list or table would flatten?
- Yes → proceed with a diagram
- No → use a numbered list, bullet list, or table instead
A 5-step linear process is a list. A 5-step process with two decision points and a retry loop is a diagram.
Diagram Selection Guide
| I need to show... |
Use |
Also consider |
| A decision or approval process |
Flowchart |
State |
| Multi-service or multi-party interactions |
Sequence |
Flowchart |
| Feature lifecycle or status transitions |
State |
Flowchart |
| Work stages or pipeline status |
Kanban |
State |
| Release or sprint timeline with dependencies |
Gantt |
Timeline |
| Version history or chronological milestones |
Timeline |
Gantt |
| 2D prioritization (effort/impact, risk/value) |
Quadrant |
- |
| Allocation breakdown or composition |
Pie |
Treemap |
| Problem decomposition or brainstorming |
Mindmap |
- |
| Domain models or data relationships |
ER |
Class |
| API or object contracts |
Class |
ER |
| System topology or infrastructure |
Architecture |
Flowchart |
| Flow quantities or budget allocation |
Sankey |
Pie |
| Hierarchical proportional data |
Treemap |
Pie |
| Trends or time-series metrics |
XY-Chart |
- |
For worked examples organized by PM task, see references/pm-use-cases.md.
For full syntax and options per type, see references/diagram-catalog.md.
Syntax Validity Principles
Six rules that prevent most rendering failures:
- Quote labels - Any label containing spaces, parentheses, brackets, colons, commas, or reserved words must be quoted with double quotes
- Escape special characters - Characters with mermaid or markdown meaning (
>, <, - at line start, #) need escaping or quoting
- Declare before referencing - Define a node before using it in an edge; referencing an undeclared node causes silent failures in some types
- Respect limits - Each diagram type has a maximum node/participant count beyond which readability collapses (see
references/diagram-catalog.md for per-type limits)
- Comment your intent - Use
%% comments to document non-obvious choices (why this layout direction, why this grouping)
- Test before shipping - Paste into a mermaid renderer (mermaid.live, VS Code preview, or your target environment) and verify it renders correctly
For the complete syntax reference, see references/syntax-guide.md.
Instructions
- Identify what you're communicating - What relationship, flow, hierarchy, or proportion needs to be visible? Who is the audience?
- Apply the cardinal rule - Confirm a diagram adds value over a list or table
- Select a diagram type - Use the selection guide above, browse
references/pm-use-cases.md by task, or browse references/diagram-catalog.md by type
- Plan the diagram - Fill out the planning worksheet in
references/TEMPLATE.md: purpose, audience, node inventory, type rationale
- Write the mermaid code - Follow
references/syntax-guide.md rules; start with the minimal syntax example from references/diagram-catalog.md and expand
- Validate - Run through the quality checklist below
- Embed - Place the validated mermaid code block in your document
Output Contract
- Planning artifact: A completed diagram planning worksheet (
references/TEMPLATE.md)
- Final output: A syntactically valid mermaid code block embedded in the target document
- Quality gate: All items in the quality checklist pass
Quality Checklist
References
| File |
Purpose |
references/TEMPLATE.md |
Diagram planning worksheet - fill out before writing mermaid code |
references/EXAMPLE.md |
Worked example: PM creating 4 diagrams for a product launch |
references/diagram-catalog.md |
All 15 diagram types: syntax, PM examples, limits, pitfalls |
references/pm-use-cases.md |
PM task → diagram type mapping with mini worked examples |
references/syntax-guide.md |
Complete syntax validity rules, escaping, styling, and validation checklist |
1---2name: utility-mermaid-diagrams3description: Teaches PMs to create syntactically valid mermaid diagrams by selecting the right diagram type for their communication need, following syntax validity rules, and validating before shipping. Covers all 15 mermaid diagram types with PM-relevant examples and a dual-lens navigation system.4license: Apache-2.05---6
7<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
8
9# Mermaid Diagrams
10
11Create effective, syntactically valid mermaid diagrams for product documents.
12
13## When to Use
14
15- Creating mermaid diagrams for PRDs, specs, roadmaps, or stakeholder presentations
16- Choosing which of 15 diagram types fits a specific communication need
17- Debugging mermaid code that won't render or renders incorrectly
18- Reviewing diagrams for clarity, accuracy, and accessibility
19
20## When NOT to Use
21
22- Exporting diagrams to image files (PNG/SVG) - that's a rendering tool concern
23- Using non-mermaid diagramming tools (Figma, Lucidchart, draw.io)
24- Creating purely decorative visuals with no informational purpose
25- Producing a full customer-journey artifact (stages, touchpoints, emotional curve, pain points) rather than a standalone diagram - use `discover-journey-map`, which composes this skill for its timeline or flowchart section
26
27## The Cardinal Rule
28
29> Don't diagram what a list can say.
30
31Diagrams earn their place when they reveal **relationships**, **branching**, or **flow** that prose flattens. Before creating any diagram, ask:
32
33*Does this show branching, relationships, or flow that a list or table would flatten?*
34
35- **Yes** → proceed with a diagram
36- **No** → use a numbered list, bullet list, or table instead
37
38A 5-step linear process is a list. A 5-step process with two decision points and a retry loop is a diagram.
39
40## Diagram Selection Guide
41
42| I need to show... | Use | Also consider |
43|-------------------|-----|---------------|
44| A decision or approval process | Flowchart | State |
45| Multi-service or multi-party interactions | Sequence | Flowchart |
46| Feature lifecycle or status transitions | State | Flowchart |
47| Work stages or pipeline status | Kanban | State |
48| Release or sprint timeline with dependencies | Gantt | Timeline |
49| Version history or chronological milestones | Timeline | Gantt |
50| 2D prioritization (effort/impact, risk/value) | Quadrant | - |
51| Allocation breakdown or composition | Pie | Treemap |
52| Problem decomposition or brainstorming | Mindmap | - |
53| Domain models or data relationships | ER | Class |
54| API or object contracts | Class | ER |
55| System topology or infrastructure | Architecture | Flowchart |
56| Flow quantities or budget allocation | Sankey | Pie |
57| Hierarchical proportional data | Treemap | Pie |
58| Trends or time-series metrics | XY-Chart | - |
59
60For worked examples organized by PM task, see `references/pm-use-cases.md`.
61For full syntax and options per type, see `references/diagram-catalog.md`.
62
63## Syntax Validity Principles
64
65Six rules that prevent most rendering failures:
66
671. **Quote labels** - Any label containing spaces, parentheses, brackets, colons, commas, or reserved words must be quoted with double quotes
682. **Escape special characters** - Characters with mermaid or markdown meaning (`>`, `<`, `-` at line start, `#`) need escaping or quoting
693. **Declare before referencing** - Define a node before using it in an edge; referencing an undeclared node causes silent failures in some types
704. **Respect limits** - Each diagram type has a maximum node/participant count beyond which readability collapses (see `references/diagram-catalog.md` for per-type limits)
715. **Comment your intent** - Use `%%` comments to document non-obvious choices (why this layout direction, why this grouping)
726. **Test before shipping** - Paste into a mermaid renderer (mermaid.live, VS Code preview, or your target environment) and verify it renders correctly
73
74For the complete syntax reference, see `references/syntax-guide.md`.
75
76## Instructions
77
781. **Identify what you're communicating** - What relationship, flow, hierarchy, or proportion needs to be visible? Who is the audience?
792. **Apply the cardinal rule** - Confirm a diagram adds value over a list or table
803. **Select a diagram type** - Use the selection guide above, browse `references/pm-use-cases.md` by task, or browse `references/diagram-catalog.md` by type
814. **Plan the diagram** - Fill out the planning worksheet in `references/TEMPLATE.md`: purpose, audience, node inventory, type rationale
825. **Write the mermaid code** - Follow `references/syntax-guide.md` rules; start with the minimal syntax example from `references/diagram-catalog.md` and expand
836. **Validate** - Run through the quality checklist below
847. **Embed** - Place the validated mermaid code block in your document
85
86## Output Contract
87
88- **Planning artifact**: A completed diagram planning worksheet (`references/TEMPLATE.md`)
89- **Final output**: A syntactically valid mermaid code block embedded in the target document
90- **Quality gate**: All items in the quality checklist pass
91
92## Quality Checklist
93
94- [ ] Diagram renders without error in target environment
95- [ ] Cardinal rule satisfied - a list or table would not communicate this more clearly
96- [ ] No linear sequences without branching, relationships, or hierarchy
97- [ ] All labels with spaces or special characters are properly quoted
98- [ ] Special characters escaped where needed
99- [ ] Node/participant count within type-specific limits
100- [ ] Colors are accessible (WCAG AA 3:1 contrast minimum, black text on light backgrounds)
101- [ ] Color is never the sole differentiator - shapes and labels also distinguish elements
102- [ ] Diagram has a descriptive title or surrounding prose context
103- [ ] `%%` comments document any non-obvious layout or grouping choices
104
105## References
106
107| File | Purpose |
108|------|---------|
109| `references/TEMPLATE.md` | Diagram planning worksheet - fill out before writing mermaid code |
110| `references/EXAMPLE.md` | Worked example: PM creating 4 diagrams for a product launch |
111| `references/diagram-catalog.md` | All 15 diagram types: syntax, PM examples, limits, pitfalls |
112| `references/pm-use-cases.md` | PM task → diagram type mapping with mini worked examples |
113| `references/syntax-guide.md` | Complete syntax validity rules, escaping, styling, and validation checklist |
product-on-purpose