bpmn-process-designlisted

Use whenever business processes or BPMN come up in any form - reading or explaining a .bpmn file or a described workflow, modelling an as-is or to-be process, reviewing a diagram for errors before it goes to a client or an engine, or optimising a process for lead time, cost, quality or automation. Covers BPMN 2.0 notation and Method-and-Style rules, generating valid BPMN XML with diagram interchange for bpmn.io/Camunda, ERP end-to-end processes (order-to-cash, purchase-to-pay, record-to-report, hire-to-retire), process analysis and process mining, and consulting workflow from capture workshop to rollout. Use it even when the user never says the word BPMN - 'map our approval flow', 'why does this take three weeks', 'draw how orders move through the company', 'should we automate this' all belong here. Triggers: bpmn, process model, swimlane, as-is, to-be, process map, workflow diagram, process optimisation, bottleneck, cycle time, camunda, bpmn.io, prozess, prozessoptimierung, ablauf modellieren, ist-prozess, s
AiNemix/bpmn-process-design-skill · ★ 0 · AI & Automation · score 70

Install: claude install-skill AiNemix/bpmn-process-design-skill

# BPMN and Process Design Model processes people can read, catch the errors that would blow up later, and improve the process rather than the picture. **Language: mirror the user.** Write the deliverable, the element labels and the findings in whatever language the user is using. The reference files and scripts are English; that is an implementation detail, not the output format. ## Four modes Work out which one applies before doing anything — they produce different artefacts. | Mode | What the user is asking | What you deliver | |---|---|---| | **1 Understand** | "What does this process do?" / a `.bpmn` file appears | plain-language walkthrough plus what stands out | | **2 Build** | "Model this for me" | a valid `.bpmn` (with DI) plus a process profile and an explicit assumption list | | **3 Review** | "Is this right?" / "Check this before we sign it off" | findings by severity, each with a location and a concrete fix | | **4 Optimise** | "How do we make this better/faster/cheaper?" | as-is to to-be delta, levers with effort and benefit, a business case with visible assumptions | For "model it and improve it", do the as-is properly first. A to-be with no credible as-is cannot be measured afterwards, which means nobody can prove the project worked. --- ## Rules that are not negotiable These are the failures that surface at the client rather than in your own review. 1. **Never write BPMN XML by hand, and never emit it token by token.** Without a `bpmndi:BPMNDiagram`