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_FAILED incidents 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