Show the specification format that create_process expects, with every node type, field, and modeling rule. Read this before writing a spec for the first time.

Generate a BPMN 2.0 diagram from a process specification and write it as a .bpmn file that Bizagi Modeler can import (File ▸ Import ▸ BPMN).

Shape positions are computed automatically with a lane-aware layered layout, so the imported diagram is readable rather than a heap of overlapping boxes. The result includes an audit of the generated model.

Args: spec: The process definition. Call get_spec_reference() for the format. output_path: Where to write the .bpmn file. Leave empty to only preview. overwrite: Replace output_path if it already exists. return_xml: Include the full XML in the response (large).

Edit an existing .bpmn file by merging changes into its specification and regenerating the diagram (with a fresh layout).

changes accepts the same keys as a spec. Lists are handled by key: a node or flow whose id matches an existing one replaces it, anything else is appended. Use "removeNodes": ["id", …] / "removeFlows": ["id", …] to delete.

Args: file_path: The .bpmn file to edit. changes: Partial specification to merge in. output_path: Where to write the result. Defaults to overwriting file_path. overwrite: Required when writing over an existing file.

Read a .bpmn file and return its structure: pools, lanes, activities, gateways, events, and the flows between them.

Note: Bizagi's native .bpm format is proprietary and cannot be read here. Export it first from Bizagi Modeler (File ▸ Export ▸ BPMN).

Args: file_path: Path to a .bpmn or .xml file. detail: "summary" (structured JSON), "outline" (readable walk-through), or "spec" (an editable specification you can pass back to create_process).

Find BPMN and Bizagi files in a folder, with a one-line summary of each .bpmn (pools, activities, gateways).

Args: directory: Folder to scan. recursive: Include sub-folders.

Audit a diagram against BPMN 2.0 correctness rules and modeling conventions, and return every finding with a concrete fix.

Checks include: missing start/end events, unreachable elements, dead ends, sequence flows crossing pools, message flows inside one pool, gateways that branch without conditions, event-based gateway targets, implicit splits, boundary events on non-activities, plus naming, documentation, lane and diagram-size conventions.

Args: file_path: A .bpmn file to audit. Mutually exclusive with spec. spec: A specification to audit before generating it. include_best_practice: Include convention findings, not only errors. format: "json" for structured findings, "markdown" for a report.

Draw the diagram as an SVG so it can be checked without opening Bizagi Modeler — same geometry the .bpmn carries, so what you see is what imports.

Args: file_path: A .bpmn file to preview. Mutually exclusive with spec. spec: A specification to preview before writing it anywhere. output_path: Where to write the .svg. Leave empty to return the markup. overwrite: Replace output_path if it exists.

Produce a Markdown process document from a .bpmn file: an outline of every pool and lane, the step-by-step flow, and optionally the audit findings.

Args: file_path: The .bpmn file to document. output_path: Where to write the .md file. Leave empty to return the text only. include_audit: Append the audit report. overwrite: Replace output_path if it exists.

Report whether Bizagi Modeler can be controlled from here: platform, whether pywinauto is installed, where BizagiModeler.exe is, whether it is running, and which document is open. Call this before the other bizagi_* tools.

Open Bizagi Modeler, optionally with a .bpm or .bpmn file.

This is the dependable desktop action — the file is passed on the command line rather than through a menu.

Args: file_path: Diagram to open. Leave empty to just start the application.

Drive Bizagi Modeler's File ▸ Import ▸ BPMN dialog for a .bpmn file.

Best-effort UI automation: ribbon shortcuts differ between Modeler versions. If it does not take, import the file by hand — it is already on disk.

Args: file_path: The .bpmn file to import.

Drive File ▸ Export ▸ BPMN for the diagram currently open in Bizagi Modeler, so it can then be read and audited by the other tools.

Best-effort UI automation; confirm the dialog on screen if nothing appears.

Args: output_path: Where Bizagi should write the .bpmn file.