Menu
Run scenario tests on a BPMN process file and report path coverage. Usage: /bpmnkit:test [file.bpmn]
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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>
Wire an existing BPMN step to an external service via a Camunda connector template. Usage: /bpmnkit:connect <file> <step-id> <service>
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]
| name | test |
| description | Run scenario tests on a BPMN process file and report path coverage. Usage: /bpmnkit:test [file.bpmn] |
Run scenario tests: $ARGUMENTS
Extract the .bpmn filename from $ARGUMENTS, or find the single .bpmn in cwd, or ask. Look for a sidecar <file>.bpmn.tests.json next to it (written automatically by casen synth from a plan's tests array). If it doesn't exist:
.plan.json for this file exists (or can be produced via casen plan extract <file>.bpmn), add a tests array covering the happy path and every gateway branch / error boundary (see references/plan-format.md), then casen synth <plan>.json --merge <file>.bpmn to regenerate the sidecar.<file>.bpmn.tests.json directly: an array of { id, name, inputs?, mocks?: { [jobType]: { outputs? } | { error? } }, expect?: { path?, variables? } }.casen test <file>.bpmn
**Scenario Results**
| Scenario | Result | Details |
|----------|--------|---------|
| happy-path | ✓ PASS | (Nms) |
| error-path | ✗ FAIL | field: expected X, got Y |
Cross-reference the process's gateway branches and error/timer boundaries against which scenarios' expect.path actually exercise them. Report any uncovered branch:
Uncovered paths:
- Gateway "check-stock" → branch "out-of-stock" has no test scenario
- Boundary "payment_error" (errorCode PAYMENT_FAILED) has no test scenario
"X/Y scenarios passed. N branch(es)/boundary(ies) uncovered."