Menu
Wire an existing BPMN step to an external service via a Camunda connector template. Usage: /bpmnkit:connect <file> <step-id> <service>
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Design and add a Camunda AI Agent Sub-process to a new or existing BPMN process — model, prompts, tools, and a mocked test scenario. Usage: /bpmnkit:agent [file] <description>
Gate a BPMN process on deploy-readiness, then deploy it to local Reebe or Camunda 8. Usage: /bpmnkit:deploy [file.bpmn] [--local|--camunda]
Extend an existing BPMN process from a natural-language change request — lifts it to a plan, applies a targeted delta, and merges. Usage: /bpmnkit:extend <file.bpmn> <change request>
Implement a BPMN process end-to-end from a natural language description — writes a ProcessPlan, compiles it deterministically, tests it, and offers to deploy. Usage: /bpmnkit:implement <description>
Run the full static analyzer on a BPMN file and report deploy-readiness. Usage: /bpmnkit:review [file.bpmn]
Run scenario tests on a BPMN process file and report path coverage. Usage: /bpmnkit:test [file.bpmn]
| name | connect |
| description | Wire an existing BPMN step to an external service via a Camunda connector template. Usage: /bpmnkit:connect <file> <step-id> <service> |
Connect a step to a service: $ARGUMENTS
Parse $ARGUMENTS into a .bpmn file, the target step's element id, and the service to connect (e.g. "slack", "send an email", "call the pricing API"). Read references/connectors.md first.
casen connector search "<service>"
Present the top match(es) to the user only if there's genuine ambiguity (e.g. multiple plausible directions — outbound vs. an inbound trigger); otherwise proceed with the best match.
casen connector show <template-id>
For every required input: derive a value from context (process variables via FEEL, or ask the user for anything that can't be inferred — especially secrets, which always become {{secrets.NAME}} placeholders, never literal credentials). Note which secret names the user needs to provision in their target engine's secret store — don't try to set them yourself.
casen plan extract <file>.bpmn
Write a delta plan replacing the target step (same element id) with a connector step:
{ "kind": "connector", "id": "<step-id>", "name": "...", "connector": { "template": "<template-id>", "values": { ... } } }
casen synth <delta>.plan.json --merge <file>.bpmn --output <file>.bpmn
casen lint lint <file>.bpmn --profile deploy
Fix any connector/missing-required findings by filling in the missing value, then re-synth.
Report what was wired (template id, task type), which values were set, and which secret names the user still needs to provision.