@bpmnkit/docspack 0.0.1

package/.llms/chunks/cli.casen.aikit-skills.md

@@ -0,0 +1,19 @@
+# casen CLI — AIKit Skills
+
+`casen` ships four lightweight, CLI-only Claude Code slash commands (no MCP server, no proxy):
+
+```sh
+casen skills install
+```
+
+| Command | Description |
+|---|---|
+| `/implement <description>` | Write a plan, compile it, test it, scaffold workers, deploy |
+| `/review <path>` | Run the full lint report and report a deploy-ready verdict |
+| `/test <path>` | Run scenario tests and report path/branch coverage |
+| `/deploy <path>` | Deploy-readiness gate, then deploy to local Reebe or Camunda 8 |
+
+For the richer skill set (`/bpmnkit:implement`, `:extend`, `:agent`, `:connect`, plus generated reference docs), install the Claude Code plugin instead: `/plugin marketplace add github:bpmnkit/monorepo` then `/plugin install bpmnkit`. See [AIKit Skills](/cli/skills/) for full documentation.
+
+---
+Source: https://docs.bpmnkit.com/cli/casen/

package/.llms/chunks/cli.casen.bpmn-generation-pipeline.md

@@ -0,0 +1,32 @@
+# casen CLI — BPMN generation pipeline
+
+Every BPMN process is authored as a `ProcessPlan` JSON file — never hand-written XML — and
+compiled deterministically:
+
+```sh
+# Print the ProcessPlan JSON format reference (schema + field notes)
+casen plan schema
+
+# Compile a plan to laid-out, deployable BPMN
+casen synth synth order-process.plan.json --output order-process.bpmn
+
+# Extend an existing process: lift it back to plan form, then merge a delta plan into it
+casen plan extract order-process.bpmn
+casen synth synth delta.plan.json --merge order-process.bpmn --output order-process.bpmn
+
+# Find and inspect a Camunda connector template
+casen connector search slack
+casen connector show io.camunda.connectors.Slack.v1
+
+# Deploy-readiness gate, then deploy
+casen lint lint order-process.bpmn --profile deploy
+casen deploy deploy order-process.bpmn                   # local Reebe
+casen deploy deploy order-process.bpmn --target camunda8 # active Camunda 8 profile
+```
+
+`casen synth` reports any problems keyed by JSON path in the plan (e.g. `steps[2].connector.values.token`) — fix the plan, never the XML, and re-run. If the plan has a `tests` array, `casen synth` also writes a `<file>.bpmn.tests.json` sidecar, runnable with `casen test <file>.bpmn`.
+
+See [Building Processes with AI](/guides/ai-implement/) and [AI Agents](/guides/ai-agents/) for full walkthroughs.
+
+---
+Source: https://docs.bpmnkit.com/cli/casen/

package/.llms/chunks/cli.casen.connection-profiles.md

@@ -0,0 +1,62 @@
+# casen CLI — Connection Profiles
+
+A profile stores the connection details for a Camunda cluster:
+
+```sh
+# Add a new profile
+casen profile add
+
+# You'll be prompted for:
+# Name: my-saas-cluster
+# Base URL: https://api.cloud.camunda.io
+# Auth type: oauth2 | bearer | none
+# Client ID, Client Secret, Audience, Token URL (for oauth2)
+```
+
+Profiles are saved to `~/.casen/profiles.json`.
+
+
+## Common Workflows
+
+### List process definitions
+
+```
+Navigate to: process → list → Enter
+
+Result:
+  bpmnProcessId                name                    ver
+  ──────────────────────────────────────────────────────────
+▶ invoice-approval              Invoice Approval          2
+  order-fulfillment             Order Fulfillment         1
+  customer-onboarding           Customer Onboarding       3
+```
+
+### Start a process instance
+
+```
+Navigate to: process → start → Enter
+
+Select process: invoice-approval
+Variables (JSON): {"invoiceId": "inv-001", "amount": 5000}
+```
+
+### Resolve an incident
+
+```
+Navigate to: incident → list → Enter
+```
+
+Select the incident with Enter, choose "Resolve" from the action menu.
+
+### Publish a message
+
+```
+Navigate to: message → publish → Enter
+
+Message name: payment-confirmed
+Correlation key: ord-456
+Variables (JSON): {"method": "card"}
+```
+
+---
+Source: https://docs.bpmnkit.com/cli/casen/

package/.llms/chunks/cli.casen.generate-bpmn-files.md

@@ -0,0 +1,28 @@
+# casen CLI — Generate BPMN files
+
+`casen generate bpmn` creates BPMN files from the command line — no interactive menu required.
+Choose a built-in template, supply a full CompactDiagram JSON definition, or patch an existing file.
+
+```sh
+casen generate bpmn --template approval --process-id leave-request
+casen generate bpmn --input order.bpmn --dump-compact   # inspect as JSON for AI
+casen generate bpmn --input order.bpmn --patch '{"elements":[...],"flows":[...]}'
+```
+
+See [casen generate](/cli/generate/) for full documentation.
+
+
+## View BPMN, DMN, and Form files
+
+`casen view` opens a local browser-based viewer. Accepts individual files, folders, or a mix.
+
+```sh
+casen view bpmn ./processes/     # all .bpmn files in a folder
+casen view dmn routing.dmn       # DMN decision table
+casen view open ./project/       # any mix of .bpmn/.dmn/.form
+```
+
+See [casen view](/cli/view/) for full documentation.
+
+---
+Source: https://docs.bpmnkit.com/cli/casen/

package/.llms/chunks/cli.casen.md

@@ -0,0 +1,80 @@
+# casen CLI
+
+`casen` is an interactive terminal UI (TUI) for managing Camunda 8. Navigate with arrow keys,
+no flags to memorize.
+
+
+## Installation
+
+```sh
+pnpm add -g @bpmnkit/cli
+```
+
+
+## Quick Start
+
+```sh
+casen
+```
+
+The main menu appears. Use ↑ ↓ to navigate, Enter to select, Escape to go back.
+
+
+## Navigation Structure
+
+```
+casen
+├── generate        — generate or modify BPMN files without the TUI
+│   └── bpmn        — templates, CompactDiagram JSON, or patch existing files
+├── view            — view BPMN, DMN, and form files in the browser
+│   ├── open        — any mix of .bpmn/.dmn/.form files or folders (auto-detect)
+│   ├── bpmn        — BPMN diagrams rendered as SVG
+│   ├── dmn         — DMN decision tables
+│   └── form        — Camunda form layouts
+├── lint            — static analysis and auto-fix for BPMN files
+│   ├── lint        — run all checks, report findings
+│   └── improve     — AI-assisted improvement suggestions
+├── story           — render a BPMN process as a narrative HTML page
+├── ask             — ask an AI assistant about your process or cluster
+├── connector       — generate element templates from OpenAPI specs
+│   ├── generate    — generate templates from a spec file or catalog entry
+│   └── catalog     — list built-in catalog entries
+├── profile         — manage connection profiles
+│   ├── list        — show all profiles
+│   ├── add         — create a new profile
+│   └── switch      — set the active profile
+├── process
+│   ├── list        — list deployed process definitions
+│   ├── start       — start a new instance
+│   ├── instances   — list running instances
+│   └── cancel      — cancel an instance
+├── job
+│   ├── list        — list active jobs
+│   ├── complete    — complete a job
+│   └── fail        — fail a job with a message
+├── incident
+│   ├── list        — list open incidents
+│   └── resolve     — resolve an incident
+├── decision
+│   ├── list        — list deployed DMN decision tables
+│   └── evaluate    — evaluate a decision with test inputs
+├── variable
+│   ├── list        — list variables for an instance
+│   └── update      — set a variable value
+├── message
+│   └── publish     — publish a message for correlation
+├── worker          — run job workers
+│   ├── <job-type>  — auto-complete worker for a job type
+│   └── start       — start scaffolded workers from ./workers/
+├── proxy           — start the local AI bridge server
+└── plugin          — manage CLI plugins
+    ├── search      — discover plugins on npm
+    ├── install     — install a plugin from npm or a local path
+    ├── list        — list installed plugins
+    ├── update      — update one or all plugins
+    ├── remove      — uninstall a plugin
+    └── info        — show details for an installed plugin
+```
+
+---
+Source: https://docs.bpmnkit.com/cli/casen/

package/.llms/chunks/cli.casen.plugins.md

@@ -0,0 +1,56 @@
+# casen CLI — Plugins
+
+casen's plugin system lets you extend the CLI with new command groups — your own organisation's
+workflows, third-party integrations, or community-built tools.
+
+### Discover plugins
+
+```sh
+# Browse all published casen plugins
+casen plugin search
+
+# Search by keyword
+casen plugin search deploy
+casen plugin search slack
+```
+
+Results are fetched live from the npm registry. Any package tagged with the `casen-plugin` keyword
+appears here.
+
+### Install a plugin
+
+```sh
+# Install from npm
+casen plugin install casen-deploy
+
+# Install a local plugin during development
+casen plugin install ./my-plugin
+```
+
+Plugins are installed into `~/.casen/plugins/` and loaded automatically the next time casen starts.
+
+### Manage installed plugins
+
+```sh
+# List installed plugins
+casen plugin list
+
+# Show full details for one plugin
+casen plugin info casen-deploy
+
+# Update a single plugin to the latest version
+casen plugin update casen-deploy
+
+# Update all installed plugins
+casen plugin update
+
+# Remove a plugin
+casen plugin remove casen-deploy
+```
+
+Once installed, plugin commands appear in the main TUI and in tab-completion alongside built-in commands.
+
+To build your own plugin, see [Plugin Authoring](/cli/plugin-authoring/).
+
+---
+Source: https://docs.bpmnkit.com/cli/casen/

package/.llms/chunks/cli.casen.worker-commands.md

@@ -0,0 +1,45 @@
+# casen CLI — Worker commands
+
+```sh
+# Run a simple auto-complete worker (for testing)
+casen worker payment-service
+
+# Start scaffolded workers from ./workers/
+casen worker start
+
+# Start a specific scaffolded worker
+casen worker start send-invoice
+```
+
+
+## MCP Server Mode
+
+`casen` can act as an MCP (Model Context Protocol) server, exposing all cluster operations
+as tools to Claude Desktop, Cursor, or any MCP client:
+
+```sh
+casen mcp
+```
+
+Configure in Claude Desktop (`claude_desktop_config.json`):
+
+```json
+{
+  "mcpServers": {
+    "camunda": {
+      "command": "casen",
+      "args": ["mcp"],
+      "env": {
+        "CAMUNDA_CLIENT_ID": "...",
+        "CAMUNDA_CLIENT_SECRET": "..."
+      }
+    }
+  }
+}
+```
+
+Now you can ask Claude: _"Show me the open incidents on the invoice-approval process"_ or
+_"Resolve all incidents on process instance 2251799813685249"_.
+
+---
+Source: https://docs.bpmnkit.com/cli/casen/

package/.llms/chunks/cli.connector.all-flags.md

@@ -0,0 +1,29 @@
+# casen connector — All flags
+
+| Flag | Description |
+|---|---|
+| `--swagger <file>` | Path to a local OpenAPI/Swagger YAML or JSON file |
+| `--api <id>` | Catalog entry ID — downloads the spec automatically |
+| `--output <dir>` | Directory to write `.json` template files into |
+| `--base-url <url>` | Override the base URL from the spec |
+| `--id-prefix <prefix>` | Reverse-DNS prefix for template IDs (e.g. `com.myorg`) |
+| `--filter <regex>` | Filter operations by `operationId` or summary |
+| `--expand-body` | Decompose top-level request body properties into individual input fields |
+| `--auth <type>` | Pre-select auth type (see below) |
+| `--format <fmt>` | `one-per-op` (default) or `array` — all templates in one file |
+| `--dry-run` | Print generated templates to stdout instead of writing files |
+
+### Auth types
+
+| Value | Description |
+|---|---|
+| `noAuth` | No authentication fields |
+| `apiKey` | Single API key field sent as a header |
+| `basic` | Username + password (HTTP Basic) |
+| `bearer` | Bearer token |
+| `oauth-client-credentials-flow` | Client ID, secret, token URL, and scopes |
+
+Auth is auto-detected from `components.securitySchemes` in the spec. Use `--auth` to override.
+
+---
+Source: https://docs.bpmnkit.com/cli/connector/

package/.llms/chunks/cli.connector.browse-the-bundled-ootb-catalog.md

@@ -0,0 +1,32 @@
+# casen connector — Browse the bundled OOTB catalog
+
+```sh
+casen connector search slack
+casen connector show io.camunda.connectors.Slack.v1
+```
+
+`search` scores the 116 bundled templates by keyword match and prints a table (template id,
+direction, task type, description). `show` prints a template's task type, direction, and its
+required/optional input keys — these are the keys a `ProcessPlan` `connector` step's `values`
+object uses (see [Building Processes with AI](/guides/ai-implement/)):
+
+```
+$ casen connector show io.camunda.connectors.Slack.v1
+Slack connector  (io.camunda.connectors.Slack.v1)
+Task type: io.camunda:slack:1
+Direction: outbound
+Create a channel or send a message to a channel or user
+
+Required inputs:
+  token (secret) — OAuth token
+  data.channel — Channel/user name/email
+  data.text — Message
+  ...
+```
+
+A field marked `(secret)` should be supplied as a `{{secrets.NAME}}` placeholder, never a literal
+credential. This is the same catalog `@bpmnkit/connectors`' `listConnectors()`/`searchConnectors()`
+expose programmatically.
+
+---
+Source: https://docs.bpmnkit.com/cli/connector/

package/.llms/chunks/cli.connector.built-in-catalog.md

@@ -0,0 +1,41 @@
+# casen connector — Built-in catalog
+
+```sh
+casen connector catalog
+```
+
+| ID | Name | Default auth |
+|---|---|---|
+| `github` | GitHub REST API | bearer |
+| `cloudflare` | Cloudflare API | bearer |
+| `stripe` | Stripe API | basic |
+| `notion` | Notion API | bearer |
+| `resend` | Resend Email API | bearer |
+| `openai` | OpenAI API | bearer |
+| `figma` | Figma API | bearer |
+| `twilio` | Twilio Messaging API | basic |
+| `slack` | Slack Web API | bearer |
+| `jira` | Atlassian Jira API | bearer |
+| `hubspot` | HubSpot CRM API | oauth-client-credentials-flow |
+| `discord` | Discord API | bearer |
+| `pagerduty` | PagerDuty API | apiKey |
+| `zoom` | Zoom API | oauth-client-credentials-flow |
+| `mailchimp` | Mailchimp API | apiKey |
+| `asana` | Asana API | bearer |
+| `sendgrid` | SendGrid Mail API | bearer |
+| `paypal` | PayPal Payments API | oauth-client-credentials-flow |
+| `plaid` | Plaid API | apiKey |
+| `vercel` | Vercel API | bearer |
+| `anthropic` | Anthropic API | apiKey |
+| `shopify` | Shopify Admin API | bearer |
+| `datadog` | Datadog API | apiKey |
+| `sentry` | Sentry API | bearer |
+| `intercom` | Intercom API | bearer |
+| `contentful` | Contentful Management API | bearer |
+| `airtable` | Airtable API | bearer |
+| `twitch` | Twitch Helix API | oauth-client-credentials-flow |
+| `klaviyo` | Klaviyo API | apiKey |
+| `brex` | Brex API | oauth-client-credentials-flow |
+
+---
+Source: https://docs.bpmnkit.com/cli/connector/

package/.llms/chunks/cli.connector.common-workflows.md

@@ -0,0 +1,50 @@
+# casen connector — Common workflows
+
+### Preview before writing
+
+Use `--dry-run` to inspect the generated JSON before committing to files:
+
+```sh
+casen connector generate --api resend --dry-run
+```
+
+### Filter to a subset of operations
+
+Large APIs (GitHub, Stripe) produce hundreds of templates. Use `--filter` to narrow it down:
+
+```sh
+# Only generate templates for issue-related operations
+casen connector generate --api github --filter "issues" --output ./templates/
+
+# Only POST and PUT operations (filter on summary/operationId)
+casen connector generate --api stripe --filter "create|update" --output ./templates/
+```
+
+### Expand request body fields
+
+By default the request body is a single FEEL `Text` field. Use `--expand-body` to decompose
+top-level properties into individual typed input fields — useful for simple, well-documented APIs:
+
+```sh
+casen connector generate --api resend --expand-body --output ./templates/
+```
+
+### All templates in one file
+
+```sh
+casen connector generate --api slack --format array --output ./templates/
+# Writes: ./templates/slack.json  (array of all templates)
+```
+
+### Override the base URL
+
+Useful when targeting a self-hosted or staging instance:
+
+```sh
+casen connector generate --swagger ./openapi.yaml \
+  --base-url https://staging-api.mycompany.com \
+  --output ./templates/
+```
+
+---
+Source: https://docs.bpmnkit.com/cli/connector/

package/.llms/chunks/cli.connector.generate-from-the-openapi-catalog.md

@@ -0,0 +1,30 @@
+# casen connector — Generate from the OpenAPI catalog
+
+The fastest way to get started. The catalog contains 30 popular APIs with pre-configured spec URLs
+and auth defaults:
+
+```sh
+# List all available catalog entries
+casen connector catalog
+
+# Generate templates for the Stripe API
+casen connector generate --api stripe --output ./templates/
+
+# Generate templates for GitHub with a custom ID prefix
+casen connector generate --api github --id-prefix com.myorg --output ./templates/
+```
+
+
+## Generate from a local file
+
+Pass any local OpenAPI 3.x or Swagger 2.x file in YAML or JSON format:
+
+```sh
+casen connector generate --swagger ./openapi.yaml --output ./templates/
+
+# JSON format works too
+casen connector generate --swagger ./api-spec.json --output ./templates/
+```
+
+---
+Source: https://docs.bpmnkit.com/cli/connector/

package/.llms/chunks/cli.connector.md

@@ -0,0 +1,20 @@
+# casen connector
+
+`casen connector` has two independent jobs: **browse** the 116 bundled Camunda 8 out-of-the-box
+connector templates (`search`/`show` — used by the AI generation pipeline to wire a plan step to
+a real service), and **generate** brand-new connector element templates from OpenAPI 3.x/Swagger
+2.x specs (`generate`/`catalog` — for APIs Camunda doesn't ship a template for).
+
+
+## Commands
+
+```
+casen connector
+├── search      — find a bundled OOTB connector template by name/keyword
+├── show        — show a bundled template's required/optional inputs
+├── generate    — generate new templates from an OpenAPI spec file or catalog entry
+└── catalog     — list all built-in OpenAPI-catalog entries (for `generate`)
+```
+
+---
+Source: https://docs.bpmnkit.com/cli/connector/

package/.llms/chunks/cli.connector.programmatic-usage.md

@@ -0,0 +1,7 @@
+# casen connector — Programmatic usage
+
+The underlying generator is available as a standalone package for use in Node.js scripts and build
+pipelines. See [`@bpmnkit/connector-gen`](/packages/connector-gen/).
+
+---
+Source: https://docs.bpmnkit.com/cli/connector/

package/.llms/chunks/cli.connector.what-gets-generated.md

@@ -0,0 +1,20 @@
+# casen connector — What gets generated
+
+Each operation in the spec becomes one Camunda element template JSON file. The template
+pre-configures a `bpmn:ServiceTask` with job type `io.camunda:http-json:1` and wires up:
+
+- **Method** and **URL** — hidden fixed fields; path parameters become FEEL expressions
+  (e.g. `="https://api.example.com/users/"+userId`)
+- **Path parameters** — individual `String` input fields
+- **Query parameters** — mapped to a FEEL context object
+- **Headers** — mapped to a FEEL context object
+- **Request body** — single FEEL `Text` field, or individual typed fields with `--expand-body`
+- **Authentication** — full 5-type auth block with visibility conditions; pre-selected to the
+  detected or specified auth type
+- **Output mapping**, **error expression**, **retries**, and **timeout** — standard connector fields
+
+Import the generated `.json` files into Camunda Modeler via
+**File → Import Element Templates** or by placing them in your `.camunda/element-templates/` directory.
+
+---
+Source: https://docs.bpmnkit.com/cli/connector/

package/.llms/chunks/cli.generate.definition-mode-ai-scripting-path.md

@@ -0,0 +1,89 @@
+# casen generate — Definition mode (AI / scripting path)
+
+Pass a full **CompactDiagram** JSON object directly. This covers all 23 BPMN element types, all event
+definition types, boundary events, sub-processes, and Zeebe extensions.
+
+```sh
+# Inline JSON
+casen generate bpmn --definition '{"id":"Definitions_order","processes":[...]}'
+
+# Pipe from a file or AI output
+cat definition.json | casen generate bpmn --output order.bpmn
+
+# Write to stdout
+echo '{"id":"Defs","processes":[...]}' | casen generate bpmn --output -
+```
+
+### Print the JSON schema
+
+Run `--help-schema` to print the full CompactDiagram reference — element types, event types,
+field descriptions, and a worked example — formatted for quick AI consumption:
+
+```sh
+casen generate bpmn --help-schema
+```
+
+### CompactDiagram structure
+
+```json
+{
+  "id": "Definitions_my-process",
+  "processes": [{
+    "id": "my-process",
+    "name": "My Process",
+    "elements": [
+      { "id": "start",  "type": "startEvent",      "name": "Start" },
+      { "id": "task1",  "type": "serviceTask",      "name": "Do Work", "jobType": "my-worker" },
+      { "id": "gw",     "type": "exclusiveGateway", "name": "OK?" },
+      { "id": "end-ok", "type": "endEvent",         "name": "Done" },
+      { "id": "end-err","type": "endEvent",         "name": "Failed", "eventType": "error" }
+    ],
+    "flows": [
+      { "id": "f1", "from": "start",  "to": "task1" },
+      { "id": "f2", "from": "task1",  "to": "gw" },
+      { "id": "f3", "from": "gw",     "to": "end-ok",  "condition": "= ok",      "name": "Yes" },
+      { "id": "f4", "from": "gw",     "to": "end-err", "condition": "= not ok",  "name": "No" }
+    ]
+  }]
+}
+```
+
+**Element types** — all 23 BPMN types supported:
+
+- Tasks: `serviceTask` `userTask` `scriptTask` `businessRuleTask` `callActivity` `sendTask` `receiveTask` `manualTask` `task`
+- Events: `startEvent` `endEvent` `intermediateCatchEvent` `intermediateThrowEvent` `boundaryEvent`
+- Gateways: `exclusiveGateway` `parallelGateway` `inclusiveGateway` `eventBasedGateway` `complexGateway`
+- Containers: `subProcess` `adHocSubProcess` `eventSubProcess` `transaction`
+
+**Event types** (`eventType` field on event elements):
+`timer` `message` `signal` `error` `escalation` `terminate` `cancel` `conditional` `link` `compensate`
+
+**Zeebe extensions:**
+
+| Field | Applies to | Effect |
+|---|---|---|
+| `jobType` | `serviceTask`, `sendTask` | Sets `zeebe:taskDefinition.type` |
+| `taskHeaders` | `serviceTask`, `sendTask` | Sets `zeebe:taskHeaders` key/value pairs |
+| `resultVariable` | `serviceTask`, `businessRuleTask` | Maps connector response to a variable |
+| `calledProcess` | `callActivity` | Sets `zeebe:calledElement.processId` |
+| `formId` | `userTask` | Sets `zeebe:formDefinition.formId` |
+| `decisionId` | `businessRuleTask` | Sets `zeebe:calledDecision.decisionId` |
+
+**HTTP connector shorthand:**
+
+```json
+{
+  "id": "http1",
+  "type": "serviceTask",
+  "name": "Call API",
+  "jobType": "io.camunda:http-json:1",
+  "taskHeaders": {
+    "url": "https://api.example.com/orders",
+    "method": "POST"
+  },
+  "resultVariable": "apiResponse"
+}
+```
+
+---
+Source: https://docs.bpmnkit.com/cli/generate/