@bpmnkit/cli 0.0.36 → 0.1.0

package/skills/review.md

@@ -1,35 +1,41 @@
 ---
-description: Review a BPMN file and report findings with severity and fix suggestions
+description: Review a BPMN file and report findings with severity and an explicit deploy-ready verdict.
 ---
 
 @.claude/aikit.md
 
-Review the BPMN file at the given path using BPMNKit's pattern advisor.
+Review the BPMN file: $ARGUMENTS
 
-## File to review
+If no file is given, find the single `.bpmn` in cwd or ask.
 
-$ARGUMENTS
+## Step 1 — Run both profiles
 
----
+```sh
+casen lint lint <file>.bpmn --profile deploy --format json
+casen lint lint <file>.bpmn --format json
+```
 
-1. Call `mcp__bpmnkit-aikit__bpmn_validate` on the path above.
+## Step 2 — Present findings grouped by severity
 
-2. Present findings grouped by severity:
+**Errors** (must fix before deploy)
+- `[element-id]` `[category]` message. Fix: suggestion, if present.
 
-**Errors** (block deployment or indicate broken process flow)
-- For each error: element IDs, message, suggested fix
+**Warnings** (should fix)
+- ...
 
-**Warnings** (best-practice violations, missing patterns)
-- For each warning: element IDs, message, suggested fix
+**Info** (consider)
+- ...
 
-**Info** (improvement suggestions)
-- For each info item: message
+## Step 3 — Offer auto-fix
 
-3. Show a summary:
-```
-Total: <n> findings — <errors> errors, <warnings> warnings, <info> info
-Auto-fixable: <n>
+If there are any findings, offer:
+
+```sh
+casen lint lint <file>.bpmn --fix
 ```
 
-4. If there are auto-fixable findings, ask: **"Apply auto-fixes?"**
-   If yes, call `mcp__bpmnkit-aikit__bpmn_update` with instruction: "Apply all auto-fixable pattern advisor suggestions"
+Re-run Step 1 afterward to confirm.
+
+## Step 4 — Explicit verdict
+
+End with: **"Deploy-ready: yes"** (zero errors from the deploy profile) or **"Deploy-ready: no — N error(s)"**.

package/skills/test.md

@@ -1,38 +1,36 @@
 ---
-description: Analyse a BPMN process — check worker coverage and validation findings
+description: Run scenario tests on a BPMN process file and report path coverage.
 ---
 
 @.claude/aikit.md
 
-Analyse the BPMN process at the given path.
+Run scenario tests: $ARGUMENTS
 
-## File to test
+If no file is given, find the single `.bpmn` in cwd or ask.
 
-$ARGUMENTS
+## Step 1 — Ensure scenarios exist
 
----
+Look for `<file>.bpmn.tests.json` (written automatically by `casen synth` from a plan's `tests` array). If missing: `casen plan extract <file>.bpmn`, add a `tests` array covering the happy path and every branch/boundary, then `casen synth <plan>.json --merge <file>.bpmn` to regenerate it — or hand-write the sidecar directly (array of `{ id, name, inputs?, mocks?, expect? }`).
 
-1. Call `mcp__bpmnkit-aikit__bpmn_read` to understand the process structure (elements, service tasks, gateways, event types).
+## Step 2 — Run
 
-2. Call `mcp__bpmnkit-aikit__bpmn_simulate` with the path and an empty scenarios array to get worker coverage and validation analysis.
+```sh
+casen test <file>.bpmn
+```
 
-3. Call `mcp__bpmnkit-aikit__worker_list` to show the full worker catalog.
+## Step 3 — Report
 
-4. Present the results:
+```
+| Scenario | Result | Details |
+|----------|--------|---------|
+| happy-path | ✓ PASS | (Nms) |
+| error-path | ✗ FAIL | field: expected X, got Y |
+```
 
-**Process structure**
-- Pools / participants
-- Service tasks and their job types
-- Decision gateways and branch conditions
-- Event types (timer, message, error, escalation)
+## Step 4 — Coverage
 
-**Worker coverage**
-- ✓ Covered job types (matched to built-in or scaffolded workers)
-- ✗ Missing job types (no worker found — scaffold with worker_scaffold)
+Cross-reference gateway branches and error/timer boundaries against which scenarios exercise them; report anything uncovered.
 
-**Validation findings**
-- Errors and warnings from the pattern advisor
+## Step 5 — Summary
 
-**Suggested test scenarios** (derived from the BPMN structure)
-- Happy path: <describe the main success path>
-- Edge cases: <describe key branches, timeouts, error conditions>
+"X/Y scenarios passed. N branch(es)/boundary(ies) uncovered."

package/skills/design.md

@@ -1,87 +0,0 @@
----
-description: Design a BPMN process — flow, forms, and decision tables. No workers, no deployment.
----
-
-@.claude/aikit.md
-
-You are designing a BPMN process using BPMNKit AIKit tools. Work through these steps in order.
-
-## Request
-
-$ARGUMENTS
-
----
-
-## Step 1 — Check for a domain pattern
-
-Call `mcp__bpmnkit-aikit__pattern_list` to see available domain patterns.
-If any pattern keywords match the request, call `mcp__bpmnkit-aikit__pattern_get` to load the full pattern as context.
-
----
-
-## Step 2 — Create the BPMN
-
-Spawn a subagent with this task:
-
-> Using `mcp__bpmnkit-aikit__bpmn_create`, generate a BPMN process for: **$ARGUMENTS**
->
-> If a pattern was loaded in Step 1, pass its readme and worker specs as context in the description parameter.
->
-> Return the file path of the generated BPMN.
-
----
-
-## Step 3 — Generate forms
-
-Spawn a subagent with this task:
-
-> Call `mcp__bpmnkit-aikit__form_create` with the BPMN path from Step 2.
->
-> Return: list of `{ taskId, formId, path }` for each form created, or an empty list if no user tasks with formId were found.
-
----
-
-## Step 4 — Generate DMN tables
-
-Spawn a subagent with this task:
-
-> Call `mcp__bpmnkit-aikit__dmn_create` with the BPMN path from Step 2.
->
-> Return: list of `{ taskId, decisionId, path }` for each DMN file created, or an empty list if no business rule tasks with decisionId were found.
-
----
-
-## Step 5 — Validate
-
-Spawn a subagent with this task:
-
-> Call `mcp__bpmnkit-aikit__bpmn_validate` on the BPMN file from Step 2.
->
-> Return: `{ errors: [...], warnings: [...] }`
-
----
-
-## Step 6 — Present design summary
-
-Collect all results and present:
-
-```
-BPMN:    <path>
-Pattern: <id or "none">
-
-Forms (<count>):
-  <formId> → <path>
-  (or "none" if empty)
-
-DMN tables (<count>):
-  <decisionId> → <path>
-  (or "none" if empty)
-
-Validation:
-  Errors:   <count> — <list if any>
-  Warnings: <count> — <list if any>
-```
-
-Then say: **"Use `/implement` to add workers, or `/deploy` when ready."**
-
-Do NOT offer to deploy.