Talk to us

Miragon AIImplement

SkillsYour coding agent makes the model deployable.

Two Claude Code plugins for the developers who make a model run. The agent sets the engine details by command and keeps your drawing, then runs one test instance on Camunda 7, CIB seven or Operaton.

Get started
Recipes on GitHub
Talk to us
bpmn-cli 0.7.0 · operate 0.7.0
# asked to make payment.bpmn deployable, the bpmn skill runsbpmn validate payment.bpmn --strictW_C7_DEPLOY_EXTERNAL_TOPIC Activity_ChargeCard:serviceTask Activity_ChargeCard is an external task withoutcamunda:topic; the engines refuse the file(`bpmn set <file> Activity_ChargeCard camunda:topic=<topic>`.)bpmn set payment.bpmn Activity_ChargeCard camunda:topic=chargebpmn validate payment.bpmn --strictvalid, 0 warning(s)# asked for one run on Operaton 2.1.5, the operate skill runsoperate deploy payment.bpmn --start --business-key B-1payment.bpmn deployed process Process_Payment 1operate advance --business-key B-1operate wait --business-key B-1 --until endedState COMPLETED

The problem

A model from Design is not yet a file the engine accepts

A coding agent without guidance does not know which details the engine checks, so an external task without a topic shows up only when the engine rejects the deployment. The agent adds such details in XML that also holds your team's drawing, and a test run means chaining REST calls and copying ids from one response into the next.

Today

  • The agent edits the XML that also holds your drawing
  • The engine reports a missing topic at deployment
  • A test run chains REST calls and copies ids along

With the skills

  • The agent changes elements by id, and your layout stays
  • bpmn validate --strict names each blocker and the command that fixes it
  • operate runs one instance by business key and checks that it ends

How it works

Your agent changes the model by command and runs it once

Validation covers Camunda 7, CIB seven and Operaton (W_C7_DEPLOY_* findings) and Camunda 8 (W_C8_DEPLOY_*). If the test instance runs into an incident, operate wait fails with exit code 9 and still shows where it stopped.

  1. Ask

    You ask in Claude Code in plain words, for example "make payment.bpmn deployable on Camunda 7, charging the card is an external task".

  2. Change

    The bpmn skill changes the model through @miragon/bpmn-cli and addresses elements by id. The agent writes no XML, and your layout stays.

  3. Validate

    bpmn validate --strict flags what the engine would refuse and names the command that fixes each finding.

  4. Run once

    The operate skill deploys the file, starts one instance, completes what it waits for and checks that it ends. It finds the instance by business key, so the agent copies no ids.

Get started

Install both plugins in Claude Code

Each plugin installs from the marketplace in its tool's repo, and each repo describes the install.

The bpmn-cli pluginThe operate plugin

Human and AI

Who does what

  • The agentMakes the file deployable and runs it onceSets the engine attributes by element id and keeps the drawing. Runs bpmn validate --strict until the file passes, then deploys to your dev engine and runs one instance to the end.
  • Your teamOwns the interfaces and the code behind themDecides the topics, job types and error codes, writes the worker or delegate code they call and reviews the change before the model goes on to Execute.

For teams

Give your whole team the same plugins

Commit both marketplaces and plugins to your repo's .claude/settings.json, so everyone who works in the repo gets them:

{
  "extraKnownMarketplaces": {
    "miragon-bpmn": { "source": { "source": "github", "repo": "Miragon/bpmn-cli" } },
    "miragon": { "source": { "source": "github", "repo": "Miragon/operate" } }
  },
  "enabledPlugins": {
    "bpmn-cli@miragon-bpmn": true,
    "operate@miragon": true
  }
}

Claude Code does not update these plugins on its own. After a release, refresh the marketplace (miragon-bpmn or miragon) and update the plugin, or turn on auto-update for both marketplaces under /plugin > Marketplaces. The details are in the docs of the bpmn-cli plugin and of the operate plugin.

Status

Where the skills stand on 14 October 2026

bpmn-cli 0.7.0 and operate 0.7.0, both released on 2026-10-14, are public under the MIT licence, and each plugin carries the version of its CLI on npm. Both are pre-1.0, and both have shipped breaking changes in minor releases.

  • Worker code is yours

    No skill writes the worker or delegate code that the topics and job types point to.

  • Camunda 8 stops at validation

    Camunda 8 gets modelling and validation only. No skill deploys to or runs on it.

  • No DMN skill

    Decision tables get no skill of their own.

  • Eval results unpublished

    We have not published eval results for either plugin yet.

  • Plugins for Claude Code

    Other coding agents can use both CLIs without a skill, through the guides the CLIs print (bpmn guide, operate guide).

  • No recorded demo

    A recorded demo of both skills on a real process application does not exist yet.

Proof you can open

Read the skills before you install them

Where it fits

Skills in the lifecycle

The model comes from Design and goes on to Execute. Miragon AI shows the whole lifecycle.

Set up the skills for your team and your engines.

Tell us which engines you run and how your developers use coding agents today. We go through where the two plugins fit and where your team still writes the code.

Talk to us

A 30-minute first call.