SKILL

okhp3-visual-process-modeling

Generate, validate, normalise, and explain Mermaid-native bpmn-beta diagrams from a Process Narrative Specification. Use this skill when the user wants to convert a PNS or process notes into a visual diagram; when they ask for BPMN, a process flow, a swimlane diagram, or a workflow diagram; when they want to validate or repair existing bpmn-beta code; when they mention pools, lanes, gateways, tasks, events, or BPMN 2.0; when they want a Mermaid-native process model they can commit to a repo; when the PNS has three or more gateway decision points and a DMN decision table is warranted. Do not use it for a non-BPMN diagram type (flowchart, sequence, ER) — use standard Mermaid syntax for those instead. Produces bpmn-beta.mmd and, optionally, a rendered process-model.svg.

Target: Software development & testing. Automatically collected · unverified.

Excerpt from the author’s documentation

Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.

Read the original English text

Topics in the source

  • okhp3-visual-process-modeling
  • Purpose
  • When to use this skill
  • When NOT to use this skill
  • PNS → bpmn-beta Mapping
  • Representation trace convention
  • DMN Trigger Rule
  • Generation Workflow

BP-SKILL: Business Process Agent Skill Suite · part of mermaid-diagram-bpmn · OverKill Hill P³ -- Generate a Mermaid-native bpmn-beta diagram from a validated PNS. The diagram uses the BPMN 2.0 Descriptive Conformance Sub-Class node set (tasks, gateways, events, message flows, pools, and lanes) expressed in the readable bpmn-beta DSL. -- PNS has validation.readyforbpmnmodeling: true User wants a visual process diagram in Mermaid syntax User wants to validate or normalise existing bpmn-beta code PNS contains ≥3 decisionpoints → also trigger okhp3-decision-model-authoring for a DMN table PNS has not been validated (score for sequence flows; > for message flows (top level only) 5. Add events: (( start )) and ([ end ]) for process boundaries; ((! error )) for exception paths 6. Validate: run scripts/validate-bpmn-beta.mjs; fix all errors 7. Normalise: run scripts/normalize-bpmn-beta.mjs for consistent whitespace and ordering 8. Lint: run scripts/lint-process-model.mjs for naming conventions and pool structure -- Rules: bpmn-beta keyword opens the diagram pool Name { } groups lanes; omit for flat (single-lane) diagrams lane Name { } defines a swimlane Message flows > must be at top leve

This is an excerpt. Refer to the complete source and its current requirements.

Source repository
OKHP3/skillz
Source file
process-capture/okhp3-visual-process-modeling/SKILL.md
Fixed revision
7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Read the complete original documentation ↗

Sources and evidence

This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.

Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:55.388Z.

Categories are inferred from names, descriptions and paths. They do not establish compatibility.

License and attribution

MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.

Original license ↗

Synchronization, copying and user-reported success do not mark a resource as runtime-tested.

Limitations and notes

  • Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.