clone

a browser-first diagram editor with live svg previews, local drafts and encrypted, accountless sharing

main
diagramzip / apps / docs / static / skills / hierarchy-diagram / SKILL.md
SKILL.md 2.1K rendered
1---2name: hierarchy-diagram3description: Use when the user needs a ranked, nested, or reporting structure such as a taxonomy, organization chart, tree, or work breakdown structure.4---56# Hierarchy diagram78## What / why910A hierarchy diagram shows parent-child levels. It tells the story “what contains, reports to, or decomposes into what?” Name the relationship because taxonomy, authority, and work decomposition are not interchangeable.1112## How to model1314- Declare the hierarchy kind and root before adding nodes.15- Give each node one parent unless multiple inheritance is explicitly intended.16- Keep siblings at the same abstraction level; avoid mixing roles, instances, and tasks.17- For a WBS, use verb-led deliverables and decompose until work is estimable; for an org chart, use roles and reporting lines; for a taxonomy, use concepts and “is-a” relationships.18- Show cross-links separately from the tree so they cannot be mistaken for parentage.1920## Styling and customization2122Use top-down or left-to-right levels, aligned siblings, consistent node sizes, and whitespace. Use color to distinguish categories or departments, not depth alone. For org charts, label role and optionally person separately; for WBS, show identifiers and status secondarily.2324## Renderer choices2526Preserve user choice. Mermaid flowcharts/mindmaps and Graphviz/DOT are good for generated trees; PlantUML can express deployment/component-style hierarchies; D2 and diagrams.net suit bespoke layouts. diagram.zip has no dedicated org-chart or WBS semantic renderer: use supported syntax and document relationship semantics in labels.2728## Review2930Verify one root (or explain a forest), consistent parent semantics, no accidental cycles, readable levels, and a legend for dashed or secondary links. Check that a WBS is deliverable-oriented rather than merely an org chart.3132## Prior art and gaps3334See [references/prior-art.md](references/prior-art.md). ArchiMate, SysML, and formal WBS interchange are not rendered as native diagram.zip semantic types; integration would require a parser/profile and conformance checks.