1{2 "version": 1,3 "groups": [4 {5 "id": "workflow",6 "label": "Routing and collaboration"7 },8 {9 "id": "behavior",10 "label": "Behavior and process"11 },12 {13 "id": "architecture",14 "label": "Software and system structure"15 },16 {17 "id": "conceptual",18 "label": "Conceptual and planning"19 },20 {21 "id": "data",22 "label": "Data visualization"23 },24 {25 "id": "technical",26 "label": "Technical and hardware"27 }28 ],29 "skills": [30 {31 "id": "diagramming",32 "label": "Choose a diagram",33 "group": "workflow",34 "role": "router",35 "question": "Which visual story best answers the reader's question?",36 "useCases": [37 "Route a diagram request by meaning",38 "Choose a renderer after choosing the story"39 ],40 "avoidWhen": [41 "The user already selected a semantic diagram type"42 ],43 "name": "diagramming",44 "description": "Choose the semantic diagram story first, then select a diagram.zip renderer and produce a clear, reviewable diagram.",45 "userInvokableOnly": false,46 "path": "/skills/diagramming/SKILL.md"47 },48 {49 "id": "diagram-workshop",50 "label": "Diagram workshop",51 "group": "workflow",52 "role": "workflow",53 "question": "What should we discover together before committing to a diagram?",54 "useCases": [55 "Facilitate an explicit, user-led diagram design session"56 ],57 "avoidWhen": [58 "A focused request can be handled directly"59 ],60 "name": "diagram-workshop",61 "description": "Work with me to discover the right diagram question, audience, scope, and level of detail before making a diagram.",62 "userInvokableOnly": true,63 "path": "/skills/diagram-workshop/SKILL.md"64 },65 {66 "id": "diagram-review",67 "label": "Review a diagram",68 "group": "workflow",69 "role": "Does the diagram tell its intended story accurately and accessibly?",70 "question": [71 "Review semantics, readability, fidelity, and accessibility"72 ],73 "useCases": [74 "The request is only to choose a diagram family"75 ],76 "name": "diagram-review",77 "description": "Review a proposed diagram for semantic fit, evidence, readability, accessibility, and renderer or standards limitations; recommend precise revisions.",78 "userInvokableOnly": false,79 "path": "/skills/diagram-review/SKILL.md"80 },81 {82 "id": "flowchart",83 "label": "Flowchart",84 "group": "behavior",85 "role": "diagram",86 "question": "What path does work follow through steps and decisions?",87 "useCases": [88 "Procedures",89 "Algorithms",90 "Decision-heavy workflows"91 ],92 "avoidWhen": [93 "Time-ordered interactions need lifelines",94 "Formal business semantics require BPMN"95 ],96 "name": "flowchart",97 "description": "Choose a flowchart when the user needs a readable decision or process path with a clear start, sequence, branch, merge, or end.",98 "userInvokableOnly": false,99 "path": "/skills/flowchart/SKILL.md"100 },101 {102 "id": "sequence-diagram",103 "label": "Sequence diagram",104 "group": "behavior",105 "role": "diagram",106 "question": "Who communicates with whom, and in what order?",107 "useCases": [108 "API calls",109 "Runtime collaborations",110 "Request and response flows"111 ],112 "avoidWhen": [113 "The main story is static structure"114 ],115 "name": "sequence-diagram",116 "description": "Choose a sequence diagram when the user needs to explain ordered messages, calls, responses, or time-dependent collaboration between participants.",117 "userInvokableOnly": false,118 "path": "/skills/sequence-diagram/SKILL.md"119 },120 {121 "id": "state-machine-diagram",122 "label": "State machine diagram",123 "group": "behavior",124 "role": "diagram",125 "question": "Which events cause an entity to change state?",126 "useCases": [127 "Lifecycle rules",128 "Protocol states",129 "UI state transitions"130 ],131 "avoidWhen": [132 "The story is a sequence of work rather than persistent state"133 ],134 "name": "state-machine-diagram",135 "description": "Choose a state-machine diagram when an entity's permitted states, event-triggered transitions, guards, and entry or exit behavior are the central story.",136 "userInvokableOnly": false,137 "path": "/skills/state-machine-diagram/SKILL.md"138 },139 {140 "id": "activity-diagram",141 "label": "Activity diagram",142 "group": "behavior",143 "role": "diagram",144 "question": "How does work flow across actions, branches, and owners?",145 "useCases": [146 "Concurrent workflows",147 "Swimlane processes",148 "UML behavioral modeling"149 ],150 "avoidWhen": [151 "The process requires executable BPMN semantics"152 ],153 "name": "activity-diagram",154 "description": "Choose an activity diagram when the user needs to explain workflow logic, parallel work, decisions, joins, and responsibility across actions.",155 "userInvokableOnly": false,156 "path": "/skills/activity-diagram/SKILL.md"157 },158 {159 "id": "bpmn-process",160 "label": "BPMN process",161 "group": "behavior",162 "role": "diagram",163 "question": "How does a formal business process coordinate work, events, and participants?",164 "useCases": [165 "Auditable business processes",166 "Message flows",167 "Exception and event handling"168 ],169 "avoidWhen": [170 "A lightweight explanatory flow is sufficient"171 ],172 "name": "bpmn-process",173 "description": "Choose BPMN when the user needs a formal business-process model with events, tasks, gateways, pools, lanes, and message or sequence flows.",174 "userInvokableOnly": false,175 "path": "/skills/bpmn-process/SKILL.md"176 },177 {178 "id": "use-case-diagram",179 "label": "Use-case diagram",180 "group": "behavior",181 "role": "diagram",182 "question": "Which actors pursue which goals through the system?",183 "useCases": [184 "Scope conversations",185 "Actor goals",186 "System boundary discussions"187 ],188 "avoidWhen": [189 "Detailed interaction order or internal design is required"190 ],191 "name": "use-case-diagram",192 "description": "Use when the user needs to explain who can achieve which externally visible goals with a system, including actors, system boundaries, and goal relationships.",193 "userInvokableOnly": false,194 "path": "/skills/use-case-diagram/SKILL.md"195 },196 {197 "id": "data-flow-diagram",198 "label": "Data-flow diagram",199 "group": "behavior",200 "role": "diagram",201 "question": "Where does data originate, move, transform, and rest?",202 "useCases": [203 "Information flows",204 "Trust-boundary analysis",205 "Data-processing overviews"206 ],207 "avoidWhen": [208 "Control flow or message timing is the main concern"209 ],210 "name": "data-flow-diagram",211 "description": "Use when the user needs to show where information originates, how processes transform it, where stores retain it, and which external entities exchange it.",212 "userInvokableOnly": false,213 "path": "/skills/data-flow-diagram/SKILL.md"214 },215 {216 "id": "timeline",217 "label": "Timeline",218 "group": "behavior",219 "role": "diagram",220 "question": "What happened, or will happen, in chronological order?",221 "useCases": [222 "Milestones",223 "Historical narratives",224 "Release evolution"225 ],226 "avoidWhen": [227 "Durations and dependencies drive the story"228 ],229 "name": "timeline",230 "description": "Use when the user needs to communicate events or milestones in chronological order, with dates, intervals, eras, or parallel tracks.",231 "userInvokableOnly": false,232 "path": "/skills/timeline/SKILL.md"233 },234 {235 "id": "gantt-chart",236 "label": "Gantt chart",237 "group": "behavior",238 "role": "diagram",239 "question": "When do tasks occur, overlap, and depend on each other?",240 "useCases": [241 "Project schedules",242 "Critical dependencies",243 "Delivery planning"244 ],245 "avoidWhen": [246 "Only milestone chronology is needed"247 ],248 "name": "gantt-chart",249 "description": "Use when the user needs a time-scaled schedule showing tasks, durations, dependencies, milestones, and progress across teams or workstreams.",250 "userInvokableOnly": false,251 "path": "/skills/gantt-chart/SKILL.md"252 },253 {254 "id": "user-journey-map",255 "label": "User journey map",256 "group": "behavior",257 "role": "diagram",258 "question": "What does a person experience across stages of a goal?",259 "useCases": [260 "Experience mapping",261 "Touchpoints",262 "Pain points and opportunities"263 ],264 "avoidWhen": [265 "The request is for system behavior without a user-experience lens"266 ],267 "name": "user-journey-map",268 "description": "Use when the user needs to understand a person’s experience across stages, touchpoints, actions, thoughts, emotions, pain points, and opportunities.",269 "userInvokableOnly": false,270 "path": "/skills/user-journey-map/SKILL.md"271 },272 {273 "id": "choose-architecture-diagram",274 "label": "Choose an architecture diagram",275 "group": "architecture",276 "role": "router",277 "question": "Which abstraction level and viewpoint will answer the architecture question?",278 "useCases": [279 "Route among landscape, context, container, component, dynamic, and deployment views"280 ],281 "avoidWhen": [282 "The user already selected an architecture view"283 ],284 "name": "choose-architecture-diagram",285 "description": "Choose the smallest architecture view that answers the stakeholder's question, then route it to a suitable diagram source.",286 "userInvokableOnly": false,287 "path": "/skills/choose-architecture-diagram/SKILL.md"288 },289 {290 "id": "system-landscape-diagram",291 "label": "System landscape diagram",292 "group": "architecture",293 "role": "diagram",294 "question": "How do systems and people relate across an organization or domain?",295 "useCases": [296 "Enterprise system portfolios",297 "Cross-system dependencies",298 "Ownership context"299 ],300 "avoidWhen": [301 "The focus is one system and its immediate environment"302 ],303 "name": "system-landscape-diagram",304 "description": "Show the systems and people across an organization or domain, emphasizing ownership and meaningful dependencies.",305 "userInvokableOnly": false,306 "path": "/skills/system-landscape-diagram/SKILL.md"307 },308 {309 "id": "system-context-diagram",310 "label": "System context diagram",311 "group": "architecture",312 "role": "diagram",313 "question": "How does one system interact with people and external systems?",314 "useCases": [315 "C4 system context",316 "Scope and boundary communication"317 ],318 "avoidWhen": [319 "Internal applications or deployable units must be shown"320 ],321 "name": "system-context-diagram",322 "description": "Explain one system in its environment by showing its users, external systems, and the relationships that matter.",323 "userInvokableOnly": false,324 "path": "/skills/system-context-diagram/SKILL.md"325 },326 {327 "id": "container-diagram",328 "label": "Container diagram",329 "group": "architecture",330 "role": "diagram",331 "question": "What deployable or runnable units make up the system?",332 "useCases": [333 "C4 containers",334 "Technology responsibilities",335 "Inter-container communication"336 ],337 "avoidWhen": [338 "Code-level components or infrastructure instances are the focus"339 ],340 "name": "container-diagram",341 "description": "Show the major deployable or runtime containers inside one software system and how they collaborate.",342 "userInvokableOnly": false,343 "path": "/skills/container-diagram/SKILL.md"344 },345 {346 "id": "component-diagram",347 "label": "Component diagram",348 "group": "architecture",349 "role": "diagram",350 "question": "Which components collaborate inside a container or subsystem?",351 "useCases": [352 "C4 components",353 "UML components",354 "Module responsibility"355 ],356 "avoidWhen": [357 "Only system-level scope is needed"358 ],359 "name": "component-diagram",360 "description": "Create a component-level view of software structure, interfaces, and dependencies when the audience needs implementation boundaries rather than deployment topology.",361 "userInvokableOnly": false,362 "path": "/skills/component-diagram/SKILL.md"363 },364 {365 "id": "architecture-dynamic-diagram",366 "label": "Architecture dynamic diagram",367 "group": "architecture",368 "role": "diagram",369 "question": "How do architecture elements collaborate for one scenario?",370 "useCases": [371 "C4 dynamic views",372 "Cross-boundary runtime stories"373 ],374 "avoidWhen": [375 "A reusable protocol sequence needs detailed lifelines"376 ],377 "name": "architecture-dynamic-diagram",378 "description": "Explain an architecture scenario over time by showing participating components, messages, and state changes for one concrete use case.",379 "userInvokableOnly": false,380 "path": "/skills/architecture-dynamic-diagram/SKILL.md"381 },382 {383 "id": "deployment-diagram",384 "label": "Deployment diagram",385 "group": "architecture",386 "role": "diagram",387 "question": "Where do software instances run, and how are they connected?",388 "useCases": [389 "Runtime topology",390 "Infrastructure mapping",391 "C4 or UML deployment views"392 ],393 "avoidWhen": [394 "Logical structure without runtime placement is enough"395 ],396 "name": "deployment-diagram",397 "description": "Show where software artifacts run, which infrastructure nodes host them, and how runtime communication crosses environments or trust boundaries.",398 "userInvokableOnly": false,399 "path": "/skills/deployment-diagram/SKILL.md"400 },401 {402 "id": "block-diagram",403 "label": "Block diagram",404 "group": "architecture",405 "role": "diagram",406 "question": "What are the major functional blocks and their interfaces?",407 "useCases": [408 "Functional decomposition",409 "System overviews",410 "Signal or responsibility boundaries"411 ],412 "avoidWhen": [413 "A stricter domain notation is required"414 ],415 "name": "block-diagram",416 "description": "Arrange labeled blocks and relationships to communicate system decomposition, signal or data paths, and high-level structure without committing to a specialized formal notation.",417 "userInvokableOnly": false,418 "path": "/skills/block-diagram/SKILL.md"419 },420 {421 "id": "class-diagram",422 "label": "Class diagram",423 "group": "architecture",424 "role": "diagram",425 "question": "What types exist and how are their structures related?",426 "useCases": [427 "Domain models",428 "Object-oriented design",429 "Static type relationships"430 ],431 "avoidWhen": [432 "The main story concerns data persistence tables"433 ],434 "name": "class-diagram",435 "description": "Create or review class diagrams that explain types, responsibilities, contracts, and structural relationships in an object-oriented or domain model.",436 "userInvokableOnly": false,437 "path": "/skills/class-diagram/SKILL.md"438 },439 {440 "id": "entity-relationship-diagram",441 "label": "Entity-relationship diagram",442 "group": "architecture",443 "role": "diagram",444 "question": "Which data entities exist and how are they related?",445 "useCases": [446 "Conceptual data models",447 "Relational schemas",448 "Cardinality review"449 ],450 "avoidWhen": [451 "Runtime object behavior is the focus"452 ],453 "name": "entity-relationship-diagram",454 "description": "Model persistent data with entities, attributes, keys, relationships, cardinality, optionality, and integrity boundaries using an entity-relationship diagram.",455 "userInvokableOnly": false,456 "path": "/skills/entity-relationship-diagram/SKILL.md"457 },458 {459 "id": "dependency-graph",460 "label": "Dependency graph",461 "group": "architecture",462 "role": "diagram",463 "question": "What depends on what, and where are cycles or critical paths?",464 "useCases": [465 "Package dependencies",466 "Build graphs",467 "Service dependencies"468 ],469 "avoidWhen": [470 "Ordered interactions or physical topology are central"471 ],472 "name": "dependency-graph",473 "description": "Show dependencies between packages, modules, services, artifacts, or concepts when the important story is coupling, direction, reachability, or change impact.",474 "userInvokableOnly": false,475 "path": "/skills/dependency-graph/SKILL.md"476 },477 {478 "id": "network-topology",479 "label": "Network topology",480 "group": "architecture",481 "role": "diagram",482 "question": "Which network zones, devices, and links connect?",483 "useCases": [484 "Logical networks",485 "Addressed segments",486 "Connectivity and trust boundaries"487 ],488 "avoidWhen": [489 "Application behavior rather than connectivity is the focus"490 ],491 "name": "network-topology",492 "description": "Document physical or logical networks with nodes, interfaces, links, segments, addressing, trust zones, and traffic boundaries.",493 "userInvokableOnly": false,494 "path": "/skills/network-topology/SKILL.md"495 },496 {497 "id": "mind-map",498 "label": "Mind map",499 "group": "conceptual",500 "role": "diagram",501 "question": "What ideas radiate from one central topic?",502 "useCases": [503 "Brainstorming",504 "Early exploration",505 "Topic decomposition"506 ],507 "avoidWhen": [508 "Relationships need explicit semantic labels"509 ],510 "name": "mind-map",511 "description": "Use when the user needs to explore one central topic through associative branches, capture brainstorming, or organize an unconstrained idea space before choosing a structure.",512 "userInvokableOnly": false,513 "path": "/skills/mind-map/SKILL.md"514 },515 {516 "id": "concept-map",517 "label": "Concept map",518 "group": "conceptual",519 "role": "diagram",520 "question": "Which concepts relate, and what do those relationships mean?",521 "useCases": [522 "Knowledge models",523 "Explanatory relationship networks"524 ],525 "avoidWhen": [526 "A single-root hierarchy is sufficient"527 ],528 "name": "concept-map",529 "description": "Use when the user needs to explain concepts and the labeled relationships between them, especially definitions, dependencies, evidence, or cross-domain connections.",530 "userInvokableOnly": false,531 "path": "/skills/concept-map/SKILL.md"532 },533 {534 "id": "hierarchy-diagram",535 "label": "Hierarchy diagram",536 "group": "conceptual",537 "role": "diagram",538 "question": "How is a set organized into parent-child levels?",539 "useCases": [540 "Trees",541 "Organization charts",542 "Work breakdown structures"543 ],544 "avoidWhen": [545 "Many-to-many relationships carry the meaning"546 ],547 "name": "hierarchy-diagram",548 "description": "Use when the user needs a ranked, nested, or reporting structure such as a taxonomy, organization chart, tree, or work breakdown structure.",549 "userInvokableOnly": false,550 "path": "/skills/hierarchy-diagram/SKILL.md"551 },552 {553 "id": "decision-tree",554 "label": "Decision tree",555 "group": "conceptual",556 "role": "diagram",557 "question": "Which choices or tests lead to which outcomes?",558 "useCases": [559 "Decision guidance",560 "Classification logic",561 "Scenario branching"562 ],563 "avoidWhen": [564 "The goal is to depict an operational process with loops"565 ],566 "name": "decision-tree",567 "description": "Use when the user needs to show a sequence of choices, branching rules, outcomes, or diagnostic paths.",568 "userInvokableOnly": false,569 "path": "/skills/decision-tree/SKILL.md"570 },571 {572 "id": "matrix-diagram",573 "label": "Matrix diagram",574 "group": "conceptual",575 "role": "diagram",576 "question": "How do items compare across two dimensions?",577 "useCases": [578 "Quadrants",579 "Responsibility matrices",580 "Pairwise relationship grids"581 ],582 "avoidWhen": [583 "Geometric set overlap or time is the main encoding"584 ],585 "name": "matrix-diagram",586 "description": "Use when the user needs to compare two dimensions, expose a portfolio or prioritization space, or show a many-to-many relationship in a grid or quadrant.",587 "userInvokableOnly": false,588 "path": "/skills/matrix-diagram/SKILL.md"589 },590 {591 "id": "set-diagram",592 "label": "Set diagram",593 "group": "conceptual",594 "role": "diagram",595 "question": "How do categories overlap or contain one another?",596 "useCases": [597 "Venn diagrams",598 "Euler diagrams",599 "Set relationships"600 ],601 "avoidWhen": [602 "Exact quantities or many sets must be compared"603 ],604 "name": "set-diagram",605 "description": "Use when the user needs to show membership, overlap, exclusion, union, intersection, or nested categories with sets.",606 "userInvokableOnly": false,607 "path": "/skills/set-diagram/SKILL.md"608 },609 {610 "id": "choose-data-visualization",611 "label": "Choose a data visualization",612 "group": "data",613 "role": "router",614 "question": "Which visual encoding best supports the analytical task and data?",615 "useCases": [616 "Comparison",617 "Trend",618 "Distribution",619 "Relationship",620 "Composition",621 "Flow",622 "Geography"623 ],624 "avoidWhen": [625 "The request is a conceptual diagram rather than a quantitative display"626 ],627 "name": "choose-data-visualization",628 "description": "Choose and design a data visualization when the user has data, a comparison, trend, distribution, relationship, flow, or geographic question but has not yet chosen a chart form. Use the simplest honest encoding, explain the story, and route the result to Vega or Vega-Lite when appropriate.",629 "userInvokableOnly": false,630 "path": "/skills/choose-data-visualization/SKILL.md"631 },632 {633 "id": "protocol-layout-diagram",634 "label": "Protocol layout diagram",635 "group": "technical",636 "role": "diagram",637 "question": "How are bits or bytes allocated within a protocol record?",638 "useCases": [639 "Packet headers",640 "Binary formats",641 "Byte-field documentation"642 ],643 "avoidWhen": [644 "Message ordering or state transitions are the focus"645 ],646 "name": "protocol-layout-diagram",647 "description": "Use when a diagram must explain the bit, byte, or word layout of a protocol message, file header, register, or binary record.",648 "userInvokableOnly": false,649 "path": "/skills/protocol-layout-diagram/SKILL.md"650 },651 {652 "id": "digital-timing-diagram",653 "label": "Digital timing diagram",654 "group": "technical",655 "role": "diagram",656 "question": "How do digital signals change relative to time and each other?",657 "useCases": [658 "Clocked logic",659 "Bus transactions",660 "Signal constraints"661 ],662 "avoidWhen": [663 "The request is for an analog waveform plot"664 ],665 "name": "digital-timing-diagram",666 "description": "Use when a diagram must show digital signals changing over time, including clocked interfaces, bus transactions, handshakes, setup/hold relationships, or waveform protocols.",667 "userInvokableOnly": false,668 "path": "/skills/digital-timing-diagram/SKILL.md"669 },670 {671 "id": "rack-diagram",672 "label": "Rack diagram",673 "group": "technical",674 "role": "diagram",675 "question": "Which equipment occupies each rack unit?",676 "useCases": [677 "Capacity planning",678 "Datacenter documentation",679 "Equipment placement"680 ],681 "avoidWhen": [682 "Logical network connectivity is the primary story"683 ],684 "name": "rack-diagram",685 "description": "Use when documenting equipment placement in a cabinet or rack, including rack units, device identity, power, network uplinks, and physical capacity.",686 "userInvokableOnly": false,687 "path": "/skills/rack-diagram/SKILL.md"688 },689 {690 "id": "wiring-harness-diagram",691 "label": "Wiring harness diagram",692 "group": "technical",693 "role": "diagram",694 "question": "How do connectors, conductors, and terminations map?",695 "useCases": [696 "Harness assembly",697 "Pin-to-pin connectivity",698 "Cable documentation"699 ],700 "avoidWhen": [701 "Circuit behavior or board-level electronics are the focus"702 ],703 "name": "wiring-harness-diagram",704 "description": "Use when the user needs to document wires, cables, connectors, splices, branches, pin mappings, or harness manufacturing/service information.",705 "userInvokableOnly": false,706 "path": "/skills/wiring-harness-diagram/SKILL.md"707 },708 {709 "id": "hdl-component-diagram",710 "label": "HDL component diagram",711 "group": "technical",712 "role": "diagram",713 "question": "How do HDL modules, ports, and signal paths connect?",714 "useCases": [715 "RTL hierarchy",716 "Module interfaces",717 "Hardware design review"718 ],719 "avoidWhen": [720 "Gate-level timing or physical wiring is the focus"721 ],722 "name": "hdl-component-diagram",723 "description": "Use when the user needs a hardware-design view of HDL entities, modules, interfaces, ports, parameters, clocks, resets, and hierarchy.",724 "userInvokableOnly": false,725 "path": "/skills/hdl-component-diagram/SKILL.md"726 },727 {728 "id": "circuit-diagram",729 "label": "Circuit diagram",730 "group": "technical",731 "role": "diagram",732 "question": "Which electronic components connect into a circuit?",733 "useCases": [734 "Schematic communication",735 "Electrical connectivity",736 "Circuit explanation"737 ],738 "avoidWhen": [739 "Physical harness routing or enclosure placement is needed"740 ],741 "name": "circuit-diagram",742 "description": "Use when the user needs an electrical or electronic schematic showing components, nets, reference designators, power, signal flow, and test points.",743 "userInvokableOnly": false,744 "path": "/skills/circuit-diagram/SKILL.md"745 },746 {747 "id": "technical-illustration",748 "label": "Technical illustration",749 "group": "technical",750 "role": "diagram",751 "question": "Which spatial or mechanical relationships must the reader see?",752 "useCases": [753 "Exploded views",754 "Annotated assemblies",755 "Physical instructions"756 ],757 "avoidWhen": [758 "Abstract relationships can be communicated more precisely with a diagram notation"759 ],760 "name": "technical-illustration",761 "description": "Use when the user needs an explanatory technical figure showing parts, assemblies, operation, dimensions, callouts, or a controlled visual sequence.",762 "userInvokableOnly": false,763 "path": "/skills/technical-illustration/SKILL.md"764 }765 ],766 "standards": [767 {768 "id": "bpmn-2.0.2",769 "name": "OMG BPMN 2.0.2",770 "status": "source-supported",771 "relatedSkills": [772 "bpmn-process"773 ],774 "note": "The BPMN renderer accepts BPMN 2.0 XML and diagram interchange data. Treat rendering as separate from complete semantic validation.",775 "source": "https://www.omg.org/spec/BPMN/2.0.2/"776 },777 {778 "id": "uml-2.5.1",779 "name": "OMG UML 2.5.1",780 "status": "visual-subset",781 "relatedSkills": [782 "use-case-diagram",783 "sequence-diagram",784 "state-machine-diagram",785 "activity-diagram",786 "class-diagram",787 "component-diagram",788 "deployment-diagram"789 ],790 "note": "PlantUML and other renderers cover useful UML views, but diagram.zip does not validate the complete metamodel or import and export UML XMI and UMLDI.",791 "source": "https://www.omg.org/spec/UML/2.5.1/",792 "integration": {793 "reward": "medium",794 "effort": "large",795 "scope": "UML XMI/UMLDI import, model validation, profile handling, and round-trip fidelity"796 }797 },798 {799 "id": "iso-5807-1985",800 "name": "ISO 5807:1985",801 "status": "visual-conventions",802 "relatedSkills": [803 "flowchart"804 ],805 "note": "General renderers can apply its flowchart conventions, but diagram.zip does not validate symbol or path conformance.",806 "source": "https://www.iso.org/standard/11955.html"807 },808 {809 "id": "rfc-2360",810 "name": "RFC 2360 packet diagram conventions",811 "status": "visual-conventions",812 "relatedSkills": [813 "protocol-layout-diagram"814 ],815 "note": "PacketDiag and Bytefield can express layouts that follow the conventions, but protocol-specific validation is not built in.",816 "source": "https://www.rfc-editor.org/rfc/rfc2360.html#section-3.3"817 },818 {819 "id": "dmn-1.5",820 "name": "OMG DMN 1.5",821 "status": "unsupported",822 "relatedSkills": [823 "decision-tree"824 ],825 "note": "Informal decision trees are supported. Decision requirements diagrams, DMN XML interchange, and FEEL evaluation are not.",826 "source": "https://www.omg.org/spec/DMN/1.5/",827 "integration": {828 "reward": "high",829 "effort": "medium-to-large",830 "scope": "DMN XML parser, decision requirements rendering, validation, and optional FEEL evaluation"831 }832 },833 {834 "id": "archimate-3.2",835 "name": "The Open Group ArchiMate 3.2",836 "status": "unsupported",837 "relatedSkills": [838 "choose-architecture-diagram",839 "system-landscape-diagram",840 "system-context-diagram",841 "container-diagram"842 ],843 "note": "Generic architecture pictures are supported, but ArchiMate viewpoints, notation rules, and model exchange are not.",844 "source": "https://www.opengroup.org/archimate-licensed-downloads",845 "integration": {846 "reward": "high",847 "effort": "large",848 "scope": "Licensed notation assets, ArchiMate 3.x model exchange, viewpoint rules, and conformance testing"849 }850 },851 {852 "id": "sysml-2.0",853 "name": "OMG SysML 2.0",854 "status": "unsupported",855 "relatedSkills": [856 "choose-architecture-diagram",857 "block-diagram",858 "component-diagram",859 "hierarchy-diagram"860 ],861 "note": "Generic blocks and relationships are supported, but SysML language semantics, textual notation, model interchange, and view validation are not.",862 "source": "https://www.omg.org/spec/SysML/2.0/",863 "integration": {864 "reward": "high",865 "effort": "very-large",866 "scope": "SysML textual or JSON parsing, KerML/SysML semantics, libraries, view generation, and conformance"867 }868 },869 {870 "id": "iec-60617-2026-db",871 "name": "IEC 60617:2026 DB",872 "status": "unsupported",873 "relatedSkills": [874 "circuit-diagram",875 "wiring-harness-diagram"876 ],877 "note": "General renderers can draw circuits and harnesses, but diagram.zip has no licensed IEC symbol library or symbol validation.",878 "source": "https://webstore.iec.ch/en/publication/2723",879 "integration": {880 "reward": "medium",881 "effort": "large",882 "scope": "Symbol licensing, searchable assets, semantic ports and nets, document rules, and conformance boundaries"883 }884 }885 ]886}