Map relationships between concepts
Make dependencies, overlaps and differences easier to inspect with a compact concept map and explanations of each connection.
What to provide
- The concepts, their context and any confirmed relationships.
Example Illustrative example
Input
Illustrative editorial example — not a recorded model test. For our fictional newsletter workflow: a draft is reviewed by an editor, an approved draft can be published, and an unapproved draft returns for revision.
Output
Draft → Editorial review → Approved draft → Publication Editorial review → Revision → Editorial review The arrows represent this team’s workflow, not proof of causation. Publication depends on approval in the supplied process; the review outcome determines which path follows.
Improve the result
- Label every connection and separate confirmed relationships from assumptions.
How to use this prompt
Label what arrows mean: order, dependency, ownership or influence. Mixing those relationships in one unexplained diagram can make a simple map misleading.
What to check in the result
A generated connection may be speculative. Mermaid output is text unless your viewer can render it, and the diagram syntax may need correction.