bpmn
- Repo stars 2,891
- Author updated Live
- Author repo skills
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @markdown-viewer · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: bpmn
description: Create business process diagrams using PlantUML syntax with BPMN, EIP, and Lean Mapping stencil…
category: engineering
runtime: no special runtime
---
# bpmn output preview
## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: bpmn
description: Create business process diagrams using PlantUML syntax with BPMN, EIP, and Lean Mapping stencil…
category: engineering
source: markdown-viewer/skills
---
# bpmn
## When to use
- Create business process diagrams using PlantUML syntax with BPMN, EIP, and Lean Mapping stencil icons. Best for workfl…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "bpmn" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 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.
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
@enduml
Diagram 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 |
Decide Fit First
Design Intent
How To Use It
Boundaries And Review