bpmn

Generate BPMN and integration diagrams with PlantUML stencil syntax.

3.1k|179|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/markdown-viewer/skills --skill bpmn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bpmn
Source: https://github.com/markdown-viewer/skills/tree/main/bpmn
Command: npx skills add https://github.com/markdown-viewer/skills --skill bpmn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable rapid creation of clear, standardized business process and integration diagrams using PlantUML stencil icons so teams can document workflows, approvals, and messaging patterns without manual drawing tools.

Core Features & Use Cases

  • Declarative stencil library for BPMN events, gateways, tasks, EIP components, and lean mapping symbols to represent complex processes.
  • Precise connection semantics for sequence flows, message flows, labeled branches, pools, lanes, and timer/error events for approval workflows, ETL pipelines, EIP messaging, sagas, and value stream maps.
  • Dozens of practical examples and patterns for order processing, approvals, customer service, microservice orchestration, and event-driven architectures.

Quick Start

Create a PlantUML BPMN diagram by declaring mxgraph stencils, connecting them with solid and dashed arrows, and wrapping the flow between @startuml and @enduml.

Frequently Asked Questions about bpmn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate BPMN diagrams using PlantUML syntax?

To generate BPMN diagrams, you declare mxgraph.bpmn, mxgraph.eip, and mxgraph.lean_mapping stencils within @startuml and @enduml blocks, then connect components using solid and dashed arrows for sequence and message flows.

Can I model approval workflows and ETL pipelines with sequence flows and gateways?

Yes, you can model approval workflows and ETL pipelines using precise connection semantics for sequence flows, message flows, gateways, pools, lanes, and timer or error events via PlantUML stencil icons.

What is the best way to document event-driven architectures and EIP messaging patterns?

Documenting event-driven architectures and EIP messaging patterns is best done using declarative stencil libraries for EIP components, connecting them with labeled branches to represent message routing and microservice orchestration.

Does this approach support value stream mapping and lean mapping symbols?

Yes, the approach supports value stream mapping by utilizing the mxgraph.lean_mapping stencil library, allowing you to represent complex processes and lean mapping symbols alongside standard BPMN events and tasks.

How do I represent pools and lanes for customer service and order processing workflows?

You represent pools and lanes for order processing workflows by grouping stencil-declared tasks and gateways, using solid arrows for internal sequence flows and dashed arrows for cross-pool message flows.

When should I not use PlantUML stencils for business process modeling?

You should avoid PlantUML stencils for business process modeling if your documentation environment cannot render @startuml/@enduml blocks or if you require manual, drag-and-drop visual drawing tools instead of declarative text syntax.