camunda-process-mgmt
Use this skill to deploy BPMN, DMN, and form resources to a Camunda 8 cluster and operate live processes via c8ctl. Use for: deploying resources, starting process instances, inspecting running instances, listing or searching definitions and incidents, resolving incidents, completing user tasks, publishing correlation messages, cancelling instances, debugging stuck processes. Do not use for: authoring the BPMN, DMN, or form content itself (use camunda-bpmn, camunda-feel, camunda-forms), or installing and configuring c8ctl itself (use camunda-c8ctl). **Workflow skill** — operate a live cluster end-to-end. Covers c8ctl deploy, run, watch, list pi, search inc, complete ut, resolve inc, publish msg, cancel pi.
camunda · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add camunda/skills --skill camunda-process-mgmtAbout this skill
name: camunda-process-mgmt description: | Use this skill to deploy BPMN, DMN, and form resources to a Camunda 8 cluster and operate live processes via c8ctl.
Use for: deploying resources, starting process instances, inspecting running instances, listing or searching definitions and incidents, resolving incidents, completing user tasks, publishing correlation messages, cancelling instances, debugging stuck processes.
Do not use for: authoring the BPMN, DMN, or form content itself (use camunda-bpmn, camunda-feel, camunda-forms), or installing and configuring c8ctl itself (use camunda-c8ctl).
Workflow skill — operate a live cluster end-to-end. Covers c8ctl deploy, run, watch, list pi, search inc, complete ut, resolve inc, publish msg, cancel pi.
Camunda Process Management
Runtime operations for Camunda 8.8+ clusters via c8ctl: deploy resources, start instances, inspect state, resolve incidents, complete tasks, publish messages, cancel instances. Single skill for everything that happens after the model is written.
Prerequisites
- Camunda 8.8+ cluster (local via c8run, SaaS, or Self-Managed)
- c8ctl CLI installed and a profile configured for the target cluster — see camunda-c8ctl for setup
Cross-References
- camunda-c8ctl: Use for c8ctl setup, cluster safety, and shared conventions (flags, profiles, output modes)
- camunda-bpmn: Use for fixing BPMN process issues found during debugging
- camunda-dmn: Use for fixing DMN decision issues —
EXTRACT_VALUE_ERROR/DECISION_EVALUATION_FAILEDincidents typically trace back to the decision file - camunda-connectors: Use for fixing connector configuration issues found during debugging
- camunda-job-workers: Use when an incident traces back to handler code rather than the process model — the worker side of
zeebe:taskDefinition type - camunda-connectors-development: Use when an incident traces back to a custom connector's runtime / registration / hosting rather than its template configuration
- camunda-feel: Use for diagnosing FEEL evaluation errors (EXTRACT_VALUE_ERROR, CONDITION_ERROR) in incidents
- camunda-process-test: Use for testing processes against an embedded Zeebe engine
Instructions
Deploying Resources
Cluster safety — ask before deploying to anything that isn't local c8run.
The globally-active c8ctl profile might still point at a shared cluster (prod, staging, customer name, …) from a previous session. A bare c8ctl deploy process.bpmn then silently writes there.
- Run
c8ctl which profilefirst. If the name suggests a shared environment, confirm with the user before deploying. - Always pass
--profile=<name>explicitly ondeployand other mutating commands (run,cancel,resolve,complete,publish,watch). - For validation deploys (just running the change once to check it works), prefer
--profile=localagainst a running c8run cluster —c8ctl cluster startif not running.
See camunda-c8ctl for the authoritative cluster-safety rules.
Example — deploy a single BPMN file to the local profile:
c8ctl deploy process.bpmn --profile=local
Deploy multiple resources at once (BPMN, DMN, forms):
c8ctl deploy process.bpmn decision.dmn approval-form.form
Deploy an entire directory (recursive):
c8ctl deploy ./my-project
Pre-deploy checks (recommended):
-
Lint BPMN before deployment:
c8ctl bpmn lint process.bpmn -
Validate DMN and form files if present (see camunda-dmn and camunda-forms workflows), then deploy only the resources that are ready.
Spring Boot resource-tree tip:
- In projects that keep deployables under
src/main/resources/, prefer deployingprocesses/,decisions/, andforms/paths explicitly. - Avoid deploying the parent
src/main/resourcesdirectory wholesale when it contains non-deployable files (application.yaml,application.properties, etc.).
Example:
c8ctl deploy \
src/main/resources/processes \
src/main/resources/decisions \
src/main/resources/forms \
--profile=local
After deploying, verify:
c8ctl list pd
c8ctl search pd --iname="MyProcess"
Each deployment creates a new version of any resource it contains. Use c8ctl list pd --fields Key,Name,Version to see versions.
Starting Process Instances
Pick the start verb by intent:
| Need | Command |
|---|---|
| Start and return immediately (default) | c8ctl create pi --id <bpmnProcessId> [--variables '{...}'] |
| Deploy + start in one shot | c8ctl run <file.bpmn> [--variables '{...}'] |
| Start and block until completion | c8ctl await pi --id <bpmnProcessId> [--variables '{...}'] |
Create an instance for a deployed process:
c8ctl create pi --id MyProcess
With input variables:
c8ctl create pi --id MyProcess --variables '{"orderId": "ORD-123", "amount": 1500}'
--id maps to <bpmn:process id="..."> (the BPMN process ID), not the numeric process-definition key.
Deploy and start in one step:
c8ctl run process.bpmn --variables '{"orderId": "ORD-123"}'
Start and block until the instance completes (useful for tests / smoke checks):
c8ctl await pi --id MyProcess --variables '{"orderId": "ORD-123"}'
With a custom request timeout:
c8ctl await pi --id MyProcess --requestTimeout 60000
Not for long-running activities. await pi uses the cluster's start-and-wait REST endpoint, which times out before any single activity that runs longer than the request timeout (LLM agents, slow HTTP calls, user tasks). The timed-out response carries no instance key, so you can't follow up on the partial run. For those processes, use c8ctl create pi and poll c8ctl get pi <key> until terminal state, or fall back to c8ctl search pi --state=ACTIVE to recover the orphaned instance after a failed await.
For scripting, run create pi with