文档生成
- 作者仓库星标 2,891
- 作者更新于 实时读取
- 作者仓库 skills
- 领域
- 工程开发
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @markdown-viewer · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明（默认跨平台）
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
---
name: bpmn
description: Create business process diagrams using PlantUML syntax with BPMN, EIP, and Lean Mapping stencil…
category: 工程开发
runtime: 无特殊运行时
---
# bpmn 输出预览
## PART A: 任务判断
- 适用问题：代码实现、重构、调试或代码审查。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)”读取原文规则，不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于代码实现、重构、调试或代码审查，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件；主要在本地完成；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 先确认触发方式
原文没有稳定的斜杠命令要求。安装验证后通常全局生效，直接在对话里点名这个 Skill 并描述任务即可。
给清楚输入和边界
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是：读取文件、写入/修改文件。
小样例验证后再放大
先用一个小任务确认它会围绕“Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)”工作；涉及文件或命令时，先看 diff、日志、预览或测试结果。
复核后再交付
检查最终产物是否包含明确结果、必要证据和下一步动作；如果输出泛泛而谈，就补充输入、边界和验收标准后重跑。
---
name: bpmn
description: Create business process diagrams using PlantUML syntax with BPMN, EIP, and Lean Mapping stencil…
category: 工程开发
source: markdown-viewer/skills
---
# bpmn
## 什么时候使用
- 把工程方向的常用动作沉淀成 Agent 可调用的技能 适合处理工程开发场景下的代码实现、调试、重构、测试或代码审查，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代…
- 面向代码实现、重构、调试或代码审查，优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件；主要在本地完成；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。 证据边界与执行链路
作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。
skill "bpmn" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Critical Rules / Mxgraph Stencil Syntax / BPMN Stencil Family (mxgraph.bpmn.)
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
}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
@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 |
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核