bpmn
Skill40 starsChanged 3 months agoMITView on GitHub
Create business process diagrams using PlantUML syntax with BPMN, EIP, and Lean Mapping stencil icons. Best for workflow automation, approval chains, message-based integration patterns, and value stream mapping.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- gr219/OpenBA-Kittheir own version, first seen Oct 25, 2026
- spmtitsolution/OpenBA-Kittheir own version, first seen Oct 20, 2026
- jack1415926/claude-skillsedited, first seen Aug 14, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- jack1415926/claude-skills★ 099% same
Wrote their own version · 2
- spmtitsolution/OpenBA-Kit★ 38same name
- gr219/OpenBA-Kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-strategy-reportSkill
- apa-arrangementSkill
- archimateSkill
- architectureSkill
- audit-report-draftSkill
- audit-risk-assessmentSkill
- audit-substantive-proceduresSkill
- beps-pillar-two-assessmentSkill
- commercial-due-diligenceSkill
- compliance-investigation-designSkill
- consulting-proposal-advisorSkill
- cross-border-investment-taxSkill
- customs-and-trade-complianceSkill
- data-analytics-anomaly-detectionSkill
- deal-structure-tax-optimizationSkill
- debt-restructuringSkill
- digital-strategySkill
- equity-incentive-taxSkill
- esg-assurance-preparationSkill
- excise-and-other-indirect-taxesSkill
- executive-compensation-taxSkill
- expatriate-tax-planningSkill
- fraud-risk-assessmentSkill
- goal-definitionSkill
- group-audit-strategySkill
- infocardSkill
- internal-audit-annual-planSkill
- internal-audit-executionSkill
- itgc-testingSkill
- ma-tax-due-diligenceSkill
- meeting-intelligenceSkill
- mindmapSkill
- office-document-editorSkill
- pdf-managementSkill
- post-merger-integrationSkill
- post-merger-tax-integrationSkill
- presentation-builderSkill
- sox-compliance-checklistSkill
- tax-compliance-calendarSkill
- tax-digital-transformationSkill
- tax-dispute-responseSkill
- tax-incentive-applicationSkill
- tax-risk-management-frameworkSkill
- tp-documentation-preparationSkill
- valuation-and-pricingSkill
- vat-compliance-optimizationSkill
- walkthrough-and-control-testingSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 0 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Every diagram starts with @startuml and ends with @enduml
- Very specific: line 33
Use left to right direction for process flows (start→end reads left-to-right)
- Very specific: line 34
Use mxgraph.bpmn.* for BPMN events, gateways, and task markers
- Very specific: line 35
Use mxgraph.eip.* for Enterprise Integration Pattern icons
- Very specific: line 36
Use mxgraph.lean_mapping.* for Value Stream Mapping symbols
- Very specific: line 37
Default colors are applied automatically — you do NOT need to specify fillColor or strokeColor
- Very specific: line 38
Use rectangle "Pool" { ...
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Business Process & Integration Diagram Generator
Quick Start: Choose diagram type → Declare stencil icons for events/gateways/tasks → Group into pools/lanes → Connect with arrow syntax → Wrap in ```plantuml fence.
⚠️ IMPORTANT: Always use
```plantumlor```pumlcode fence. NEVER use```text— it will NOT render as a diagram.
When To Use / Diagnostic Intake
适用于业务流程、消息集成或价值流示意。先确认角色、开始/结束事件、异常路径、等待条件,以及用户是否需要可执行流程模型。
Workflow
逐条列出正常与异常路径→选择 BPMN/EIP/Lean 图形→设置角色边界→核对分支汇合→生成并渲染 PlantUML。
Tools and Dependencies
依赖支持本包 stencil 的 PlantUML。图形输出不是 BPMN 2.0 执行文件;需要执行语义时明确后续建模接口。
Critical Rules
- Every diagram starts with
@startumland ends with@enduml - Use
left to right directionfor process flows (start→end reads left-to-right) - Use
mxgraph.bpmn.*for BPMN events, gateways, and task markers - Use
mxgraph.eip.*for Enterprise Integration Pattern icons - Use
mxgraph.lean_mapping.*for Value Stream Mapping symbols - Default colors are applied automatically — you do NOT need to specify
fillColororstrokeColor - Use
rectangle "Pool" { ... }for BPMN pools and lanes - Sequence flows use
-->, message flows use..>(dashed)
Full stencil reference: See stencils/README.md for 9500+ available icons.
Mxgraph Stencil Syntax
mxgraph.<library>.<icon> "Label" as <alias>BPMN Stencil Family (mxgraph.bpmn.*)
Events — Circle shapes for process triggers and outcomes:
| Icon | Meaning |
mxgraph.bpmn.event.start | Start Event |
mxgraph.bpmn.event.end | End Event |
mxgraph.bpmn.event.terminateEnd | Terminate End |
mxgraph.bpmn.event.timerStart | Timer Start |
mxgraph.bpmn.event.timerCatching | Timer Intermediate |
mxgraph.bpmn.event.messageStart | Message Start |
mxgraph.bpmn.event.messageCatching | Message Catching |
mxgraph.bpmn.event.messageEnd | Message End |
mxgraph.bpmn.event.errorEnd | Error End |
mxgraph.bpmn.event.errorBound | Error Boundary |
mxgraph.bpmn.event.signalStart | Signal Start |
mxgraph.bpmn.event.signalEnd | Signal End |
Gateways — Diamond shapes for branching/merging:
| Icon | Meaning |
mxgraph.bpmn.gateway2.exclusive | Exclusive Gateway (XOR) |
mxgraph.bpmn.gateway2.parallel | Parallel Gateway (AND) |
mxgraph.bpmn.gateway2.inclusive | Inclusive Gateway (OR) |
mxgraph.bpmn.gateway2.complex | Complex Gateway |
Tasks — Use rectangle for tasks, stencil markers for typed tasks:
| Icon | Meaning |
mxgraph.bpmn.user_task | User Task |
mxgraph.bpmn.service_task | Service Task |
mxgraph.bpmn.script_task | Script Task |
mxgraph.bpmn.manual_task | Manual Task |
mxgraph.bpmn.business_rule_task | Business Rule Task |
Data — Document-like shapes:
| Icon | Meaning |
mxgraph.bpmn.data2.dataObject | Data Object |
mxgraph.bpmn.data2.dataInput | Data Input |
mxgraph.bpmn.data2.dataOutput | Data Output |
EIP Stencil Family (mxgraph.eip.*)
| Icon | Meaning |
mxgraph.eip.messageChannel | Message Channel |
mxgraph.eip.deadLetterChannel | Dead Letter Channel |
mxgraph.eip.content_based_router | Content-Based Router |
mxgraph.eip.message_filter | Message Filter |
mxgraph.eip.splitter | Splitter |
mxgraph.eip.aggregator | Aggregator |
mxgraph.eip.message_translator | Message Translator |
mxgraph.eip.content_enricher | Content Enricher |
mxgraph.eip.messaging_gateway | Messaging Gateway |
mxgraph.eip.channel_adapter | Channel Adapter |
mxgraph.eip.messaging_bridge | Messaging Bridge |
mxgraph.eip.recipient_list | Recipient List |
mxgraph.eip.wire_tap | Wire Tap |
mxgraph.eip.event_driven_consumer | Event-Driven Consumer |
mxgraph.eip.competing_consumers | Competing Consumers |
mxgraph.eip.process_manager | Process Manager |
Lean Mapping Stencil Family (mxgraph.lean_mapping.*)
| Icon | Meaning |
mxgraph.lean_mapping.outside_sources | Supplier / Customer |
mxgraph.lean_mapping.manufacturing_process | Process Step |
mxgraph.lean_mapping.supermarket | Supermarket (Inventory Buffer) |
mxgraph.lean_mapping.fifo_lane | FIFO Lane |
mxgraph.lean_mapping.production_kanban | Production Kanban |
mxgraph.lean_mapping.withdrawal_kanban | Withdrawal Kanban |
mxgraph.lean_mapping.signal_kanban | Signal Kanban |
mxgraph.lean_mapping.truck_shipment | Truck Shipment |
mxgraph.lean_mapping.operator | Operator |
mxgraph.lean_mapping.inventory_box | Inventory |
mxgraph.lean_mapping.kaizen_lightening_burst | Kaizen Burst |
mxgraph.lean_mapping.mrp_erp | MRP / ERP System |
mxgraph.lean_mapping.warehouse | Warehouse |
mxgraph.lean_mapping.push_arrow | Push Arrow |
mxgraph.lean_mapping.timeline2 | Timeline |
Connection Types
| Syntax | Meaning | Use Case |
A --> B | Solid arrow | Sequence flow (task→task) |
A ..> B | Dashed arrow | Message flow (cross-pool) / async trigger |
A --> B : "label" | Labeled solid | Conditional flow (gateway branch) |
A ..> B : "label" | Labeled dashed | Named message / signal |
Quick Example
@startuml
left to right direction
mxgraph.bpmn.event.start "Start" as start
rectangle "Review\nRequest" as review
mxgraph.bpmn.gateway2.exclusive "Approved?" as gw
rectangle "Process\nOrder" as process
rectangle "Notify\nRejection" as reject
mxgraph.bpmn.event.end "End" as end_ok
mxgraph.bpmn.event.end "End" as end_fail
start --> review
review --> gw
gw --> process : "Yes"
gw --> reject : "No"
process --> end_ok
reject --> end_fail
@endumlDiagram Types
| Type | Purpose | Key Stencils | Example |
| Order Processing | E-commerce / fulfillment | mxgraph.bpmn.event.*, mxgraph.bpmn.gateway2.* | order-processing.md |
| Approval Workflow | Multi-level approval | mxgraph.bpmn.event.*, mxgraph.bpmn.gateway2.* | approval-workflow.md |
| EIP Messaging | Message routing & transformation | mxgraph.eip.* | eip-messaging.md |
| ETL Pipeline | Data extraction & loading | mxgraph.bpmn.event.*, mxgraph.eip.* | etl-pipeline.md |
| Value Stream | Lean manufacturing flow | mxgraph.lean_mapping.* | value-stream.md |
| Microservice Orchestration | Service choreography | mxgraph.bpmn.event.*, mxgraph.eip.* | microservice-orchestration.md |
| Event-Driven Architecture | Pub/Sub event flows | mxgraph.bpmn.event.*, mxgraph.eip.* | event-driven.md |
| Customer Service | Support ticket lifecycle | mxgraph.bpmn.event.*, mxgraph.bpmn.gateway2.* | customer-service.md |
Capability Upgrade
Mode Selection
- Quick: 把文字流程转成基础 BPMN。
- Standard: 补齐泳道、事件、网关、任务、异常路径和消息流。
- Deep: 结合角色职责、系统边界、审批规则、SLA 和异常场景,形成流程优化或自动化设计图。
Process Modeling Logic
先确定流程边界、开始/结束事件、参与角色和关键决策点。没有明确事件和责任人的流程不应直接画成最终 BPMN。
Quality Gates
- 每个泳道对应真实角色、部门或系统。
- 网关条件互斥且完整。
- 异常、退回、超时和取消路径已处理。
- 消息流和顺序流没有混用。
- 输出包含图和流程说明,便于业务复核。
Deliverable Catalog
| Deliverable | When to use | Minimum content | Format |
| BPMN process diagram | 文字流程转图 | 开始/结束、任务、泳道、网关、异常路径 | PlantUML / Markdown |
| Process narrative | 业务复核 | 流程目标、角色、输入、输出、规则和异常 | Word / Markdown |
| Approval workflow map | 审批流程 | 申请、审批层级、条件、退回、超时和通知 | BPMN / PPT |
| Integration flow diagram | 系统/消息流 | 发送方、接收方、消息、转换、错误处理 | BPMN / EIP |
| Process improvement backlog | 流程优化 | 痛点、根因、改进项、owner、优先级和收益 | Excel / Tasks |
| BPMN QA checklist | 发布前 | 泳道、网关、事件、异常、命名和可读性检查 | Checklist |
Delivery Verification Materials
- 场景与预期交付:合成案例及缺失输入、注入指令变体。
- 逐项验收依据:本能力特有的检查项与复核记录。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

