AI Agent Hub
Back to skills
Visio UML Diagram Generator icon

Visio UML Diagram Generator

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_6090b166/visio-uml-generate according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem It Solves

Turning requirements into Visio UML diagrams often means manually arranging classes, relationships, lifelines, and control flow. UML-Visio-generate is for that repetitive workflow: it starts from a text description and produces a deliverable Microsoft Visio .vsdx file, reducing manual layout and format conversion.

How It Works

The skill first analyzes the input text to identify the UML diagram type and elements, then generates a structured JSON definition, and finally runs scripts/generate_vsdx.py to build the .vsdx file. It supports:
- Class diagrams: classes, interfaces, attributes, methods, inheritance, composition, and dependencies.
- Use case diagrams: actors, use cases, associations, include, and extend relationships.
- Sequence diagrams: participants, lifelines, synchronous/asynchronous/return messages.
- Activity diagrams: action nodes, decisions, start/end states, and control flow.

Under the hood, the script constructs the .vsdx as a ZIP + XML package from scratch. It applies automatic layout by diagram type: grid-style class diagrams, left/right use case diagrams, vertical sequence timelines, and vertical activity flows. Elements are color-coded, such as blue for classes, green for interfaces, yellow for use cases, and cyan for activities. Connectors also adjust arrow or line style by relationship type, such as hollow triangles for inheritance, dashed lines for dependencies, and diamonds for composition.

Boundaries

The provided test results cover four UML types, but the documentation does not state compatibility with complex documents, collaboration permissions, or Visio version differences. If the input lacks relationship types, actor names, or message ordering, the output may need manual correction. It is better suited for turning clear requirements into first drafts or presentation diagrams than replacing full architecture review.

Use Cases

  • Before a requirements review, turn a business process description into a Visio activity diagram with start, end, decision, and control-flow nodes.
  • Draft a design document by converting service-call relationships into a sequence diagram with participants, lifelines, and messages as .vsdx.
  • When inheriting a legacy system, generate a Visio class diagram from notes about classes, interfaces, inheritance, composition, and dependencies.
  • Prepare demo material by converting actor and system use cases into a Visio use case diagram with include and extend relationships.

Best For

  • Backend engineers preparing technical reviews who need to turn service calls and class relationships into Visio sequence or class diagrams.
  • Architects writing design docs who need to convert requirements text into activity or use case diagrams instead of drawing manually.
  • Developers maintaining legacy systems who need class diagrams from existing notes to inspect inheritance, composition, and dependencies.
  • Solution engineers preparing demos who need editable .vsdx use case diagrams from actor and system descriptions.