@kontextmind/kxm 0.6.0 → 0.7.4

package/docs/skills/repo-work-delivery.md

@@ -0,0 +1,107 @@
+# Repository Work Delivery Skill
+
+## Purpose
+
+`repo-work-delivery` is a reusable skill for converting an engineering request into an evidence-based, executable delivery prompt. It is designed for repository work that may need discovery, official documentation research, phased delivery, validation, pull requests, CI/review follow-through, policy-gated merge, and safe cleanup.
+
+The canonical skill is located at:
+
+```text
+.agents/skills/repo-work-delivery/SKILL.md
+```
+
+## What it does
+
+The skill requires the executor to:
+
+- Inspect repository instructions, architecture, workflow guidance, CI, package manifests, and existing patterns.
+- Identify material ambiguity and ask focused questions only when repository evidence cannot safely resolve it.
+- Select the workflow recommended by the repository’s workflow guide.
+- Assign explicit delivery roles, even when one agent performs several roles.
+- Use a one-shot workflow only for genuinely small, low-risk, self-contained changes.
+- Research fresh official documentation for every materially affected package, framework, SDK, platform, or API.
+- Create and maintain a living Markdown plan for multi-phase work.
+- Deliver buildable and testable phases with coherent commits and incremental pushes.
+- Run targeted and broader validation, record commands and outcomes, and inspect the final diff for security issues.
+- Create a pull request, monitor checks/reviews, apply only bounded low-risk fixes, and stop for user direction when scope or risk materially changes.
+- Auto-merge only where explicit authorization and repository policy allow it.
+- Clean up the workspace only after merge is verified and no local work can be lost.
+
+## Workflow selection
+
+The skill first reads the repository workflow guide. For KXM, that includes:
+
+```text
+.agents/skills/kxm-workflow/SKILL.md
+```
+
+It chooses the least complex safe workflow prescribed by that guidance.
+
+### One-shot work
+
+One-shot is suitable only when all of the following are true:
+
+- Scope is narrow and unambiguous.
+- The change is self-contained and can be validated as a single coherent unit.
+- No migration, public contract, authorization/security, irreversible side effect, or production-rollout complexity is involved.
+- No cross-service coordination is needed.
+- Repository policy does not require a phased plan.
+
+One-shot work still performs discovery, documentation research, focused validation, commit, push, and required PR work.
+
+### Phased work
+
+All other work uses a living plan. Each phase has an objective, owner role, dependencies, expected files, acceptance criteria, test commands, rollback notes when appropriate, commit boundary, and push requirement.
+
+## Required role coverage
+
+The generated prompt assigns relevant roles from this set:
+
+| Role | Primary responsibility |
+|---|---|
+| Delivery lead | Scope, decisions, workflow, plan, and final reporting |
+| Repository analyst | Architecture, instructions, existing patterns, affected paths |
+| Documentation researcher | Fresh official package/API/framework evidence |
+| Implementer | Minimal compatible code and configuration changes |
+| Test engineer | Focused, regression, integration, and acceptance validation |
+| Security reviewer | Secrets, dependencies, input handling, auth, and data-risk review |
+| Release/CI owner | Required checks, CI monitoring, and safe remediation |
+| Reviewer/merge steward | PR, review resolution, policy gates, merge, and cleanup |
+
+## Gap questions
+
+The skill asks the user only when unanswered details would materially affect behavior, scope, data/migration choices, permissions, external integrations, rollout, acceptance criteria, or merge authority. It does not ask for facts that can be established from the repository or official docs.
+
+## Documentation standard
+
+For material dependencies, research uses official maintainer or other authoritative primary documentation for the repository’s actual version. The plan or PR records the source, version/date where available, retrieval date, and decision supported.
+
+## Merge and cleanup safety
+
+Auto-merge happens only after explicit authorization or policy authorization, passing required checks, required approvals, resolved comments, clean security status, and compliance with branch protection.
+
+After verified merge, cleanup is guarded by checks for a clean workspace and fully merged branch. It updates the default branch, removes only safe merged local branches/worktrees, prunes stale references, and never discards uncommitted or user-owned artifacts.
+
+## Expected generated prompt sections
+
+A prompt produced with this skill includes:
+
+1. Desired outcome and acceptance criteria
+2. Gap-resolution gate
+3. Repository discovery
+4. Workflow selection and rationale
+5. Assigned roles
+6. Fresh official documentation research
+7. Scope, non-goals, assumptions, and constraints
+8. Design and integration expectations
+9. One-shot or phase plan
+10. Tests and validation
+11. Commit/push discipline
+12. PR, CI/review monitoring, bounded remediation, and merge gate
+13. Verified post-merge cleanup
+14. Completion report
+
+## Related
+
+- [Agent Skills](../agent-skills.md) — bundled command-suite skills
+- [Skill candidate lifecycle](../skills.md) — governed `kxm skills` candidates

package/docs/skills.md

@@ -2,6 +2,8 @@
 
 KXM turns verified episodes and lessons into reusable Agent Skills through a governed lifecycle. Runtime experience never becomes promoted skill content automatically, and promoted skills never grant tool or permission authority.
 
+This page is the governed `kxm skills` lifecycle. For the bundled command-suite skills, see [Agent Skills](agent-skills.md). For converting a repository request into a delivery prompt, see [Repository work delivery](skills/repo-work-delivery.md).
+
 ## Lifecycle
 
 ```text

package/docs/test-matrix.md

@@ -78,13 +78,14 @@ exercised from `node_modules`.
 | Non-blocking delegation | `examples/README.md` | Uses send, independent work, and get |
 | Obsolete-work cancellation | `examples/README.md` | Uses cancel and states rollback boundary |
 | Safe network retry | `examples/README.md` | Uses stable idempotency keys |
-| Jira issue-to-merge workflow | `.kxm/config/workflows/jira-development.json` | Parsed, type-checked through workflow tests, and exercised end to end with representative configuration |
+| Jira issue-to-merge workflow | `.kxm/workflows/default.yaml` | Parsed, type-checked through workflow tests, and exercised end to end with representative configuration |
 | `.kxm` workspace defaults and persisted hub/worker logs | `.kxm/`, `test/core/server.test.ts`, `test/core/worker.test.ts` | Executed with isolated temporary workspaces |
 | Signed external result callback | `examples/workflow-signal.ts` | Type-checked; equivalent signed callback path is exercised end to end in `test/core/hub-api.test.ts` |
-| Peer provenance and optional explicit degradation | `examples/provenance-workflow.json`, `.kxm/config/workflows/provenance-quorum.json`, `docs/provenance-gates.md` | Both definitions are parser-checked in `test/core/examples.test.ts`; adversarial evidence and degradation behavior is automated in `test/core/workflow-provenance.test.ts` |
+| Peer provenance and optional explicit degradation | `examples/provenance-workflow.json`, `.kxm/workflows/default.yaml`, `docs/provenance-gates.md` | Both definitions are parser-checked in `test/core/examples.test.ts`; adversarial evidence and degradation behavior is automated in `test/core/workflow-provenance.test.ts` |
 | Quorum parser boundaries and definition identity | `plugins/kxm/src/workflow.ts`, `test/core/workflow-quorum.test.ts`, `test/core/workflow-definition-hash.test.ts` | Rejects impossible peer pools, verifies degradation bounds, and proves secret-free semantic hash stamping plus credential-rotation invariance |
 | Artifact existence and containment gate | `plugins/kxm/src/artifacts-exist.ts`, `test/core/artifacts-exist.test.ts` | Non-empty regular files pass; missing, empty, non-file, lexical escape, and real-path escape cases fail closed (host-permitted symlink coverage) |
-| Headless harness helper | `scripts/harness-run.mjs`, `justfile`, `test/core/harness-run.test.ts` | Offline auth success/logout/garbage, role/mode/pair/provider refusals before spawn, missing brief/schema fail closed with zero spawn, invocation-cwd relative `prompt_file`/`output_schema` vs `request.cwd` (absolute argv tokens; Claude/Codex stdin matches the brief), Pi JSONL multi-`message_end` sums, Claude auxiliary usage, native error-on-exit-0, timeout/empty payload, sidecar-only stderr/answer/error, shell:false argv metacharacters, and win32 `.cmd` rejection. Result v2 transport vs closed model claims, dispatch-before-spawn, grok/codex isolation flags, `max_turns` validation, obsolete v1 diagnosis without rewrite or unknown-schema echo, partial usage on fail/interrupt, signaled null `exitCode` plus exact `signal`, exit-before-stdio-close drain vs bounded linger, type-closed usage/cost (no object leak or zero-coercion), malformed optional text as run-stage failure with retained spend, stdin/pid-record write failures not completed, bounded timeout settle without descendant-death claims, spawn/write-failure stage and spend, and capability-fixture parser evidence (Codex `--ignore-user-config` is not invented in top-level help; captured help bytes are not rescrubbed). Recipe quoting is covered from the justfile body without a just binary (POSIX `sh` + positional argv; Windows uses the recipe's `node -e` / argv shape). Real just integration is optional and skipped when the binary is absent. No live paid smoke. |
+| Harness inventory probe | `plugins/kxm/src/vnext-harness.ts`, `test/core/vnext-harness.test.ts` | Detect/auth/dispatch for the builtin catalog; win32 `.exe` / inner npm-package `.exe` / `.cmd` candidate order for npm shims (issue #168); `windows_shim` issue only when the shim answered; allowlisted `name.cmd` shell spawn only; rejected metacharacter commands; Linux still `not_detected` when the bare command is missing. |
+| Headless harness helper | `scripts/harness-run.mjs`, `justfile`, `test/core/harness-run.test.ts` | Offline auth success/logout/garbage, role/mode/pair/provider refusals before spawn, missing brief/schema fail closed with zero spawn, invocation-cwd relative `prompt_file`/`output_schema` vs `request.cwd` (absolute argv tokens; Claude/Codex stdin matches the brief), Pi JSONL multi-`message_end` sums, Claude auxiliary usage, native error-on-exit-0, timeout/empty payload, sidecar-only stderr/answer/error, shell:false argv metacharacters, win32 `.cmd` rejection, and win32 npm inner `claude.exe` / Pi `node.exe`+`cli.js` unwrap. Result v2 transport vs closed model claims, dispatch-before-spawn, grok/codex isolation flags, `max_turns` validation, obsolete v1 diagnosis without rewrite or unknown-schema echo, partial usage on fail/interrupt, signaled null `exitCode` plus exact `signal`, exit-before-stdio-close drain vs bounded linger, type-closed usage/cost (no object leak or zero-coercion), malformed optional text as run-stage failure with retained spend, stdin/pid-record write failures not completed, bounded timeout settle without descendant-death claims, spawn/write-failure stage and spend, and capability-fixture parser evidence (Codex `--ignore-user-config` is not invented in top-level help; captured help bytes are not rescrubbed). Recipe quoting is covered from the justfile body without a just binary (POSIX `sh` + positional argv; Windows uses the recipe's `node -e` / argv shape). Real just integration is optional and skipped when the binary is absent. No live paid smoke. |
 | Long-lived headless coordinator | `scripts/kxm-worker.mjs` | Restart limits, spawn failure, collision-resistant ownership, exact resource and tool loading, raw-output isolation, bounded RPC framing, bounded drain, hung-tool recovery, provider/model fallback, and `--continue` fallback are automated; the opt-in real-Pi gate verifies two workers, discovery, request/reply, fanout, durable restart/resume, journal, and checkpoint |
 | GitHub check signal adapter | `plugins/kxm/src/github-watch.ts` | Deterministic pagination, conclusion, retry, and per-wait delivery-generation states in `test/core/github-watch.test.ts` |
 | Operator CLI | `scripts/kxm.mjs` | Isolated workspace commands in `test/core/cli.test.ts`; the packed artifact is installed locally and with the documented global `--omit=peer` path by `test/core/package-install.test.ts` |

package/docs/troubleshooting.md

@@ -28,7 +28,7 @@ Set `KXM_WORKER_TOOL_TIMEOUT_MS` above the longest legitimate tool call. Its 31-
 
 ### A hub or worker PID claim is stale
 
-Version 0.4.3 prevents a second wrapper from replacing a live hub or worker claim. `kxm hub stop` ignores an invalid, non-running, or ownership-mismatched record rather than guessing. If a crash or pre-0.4.3 process left one behind, inspect the exact `.pid` JSON and verify that its recorded PID is no longer running; for a hub, also verify the configured port has no listener. Then remove only that exact `.pid` and its recorded `.stop` control file before relaunching once. Worker filenames include a project/agent identity digest and their records include the exact names and generation, so do not substitute a similarly sanitized filename. Never delete the `.kxm/state` directory or SQLite database to clear a claim.
+Version 0.4.3 prevents a second wrapper from replacing a live hub or worker claim. `kxm hub stop` ignores an invalid, non-running, or ownership-mismatched record rather than guessing. A hub claim whose wrapper PID is dead is reclaimed automatically on the next `kxm hub start`; the wrapper also terminates an orphaned hub server child recorded by a dead wrapper (for example after `SIGKILL`) before reclaiming, and `kxm hub stop` can stop such an orphan directly. If a pre-0.4.3 process left a malformed claim behind, inspect the exact `.pid` JSON and verify that its recorded PID is no longer running; for a hub, also verify the configured port has no listener. Then remove only that exact `.pid` and its recorded `.stop` control file before relaunching once. Worker filenames include a project/agent identity digest and their records include the exact names and generation, so do not substitute a similarly sanitized filename. Never delete the `.kxm/state` directory or SQLite database to clear a claim.
 
 ### GitHub checks passed but the workflow is still waiting
 
@@ -44,6 +44,14 @@ Set `KXM_PORT` to a valid integer. Remove the variable to use `7331`.
 
 Either restore `KXM_HOST=127.0.0.1` or configure a token before using a non-loopback interface.
 
+**`KXM hub env file is malformed`**
+
+The persisted credential file (`hub-env.json` under the user state root) failed
+validation. It holds only `KXM_AUTH_TOKEN` / `KXM_PROJECT_TOKENS` values in
+`kxm.hub-env.v1` schema; fix its JSON or delete it to have kxm generate a
+fresh admin token on the next start. To rotate the generated token, delete
+the file and run `kxm hub start` again.
+
 #### Database schema is newer than this runtime supports
 
 Do not delete or rewrite the database. Start the package version that created it, or upgrade this runtime. Restore the pre-upgrade backup when rolling back.
@@ -52,6 +60,25 @@ Do not delete or rewrite the database. Start the package version that created it
 
 Another process owns the port. Stop that process or choose another port, then update every agent's `KXM_SERVER_URL`.
 
+### `kxm harness list` says Claude Code is `not_detected` on Windows
+
+npm installs Claude Code as `claude.cmd` (and an extensionless shim), not
+`claude.exe` on `PATH`. The native binary lives next to the shim at
+`%AppData%\Roaming\npm\node_modules\@anthropic-ai\claude-code\bin\claude.exe`.
+Older probes spawned `claude` without a shell, got `ENOENT` or `EINVAL`, and
+reported the CLI missing even when `claude --version` worked in cmd or Git Bash.
+
+Current `kxm harness list` retries `claude.exe`, then that inner package
+`.exe`, then `claude.cmd` on win32. It sets `issues: ["windows_shim"]` only
+when the npm shim is what answered. If the entry is still `not_detected`,
+confirm `%AppData%\Roaming\npm` is on `PATH` for the same process that runs
+`kxm`, then `claude --version` and `claude auth status`. Assignment dispatch
+(`just assign` / `harness-run`) follows the inner `claude.exe` (and Pi's
+`node.exe` plus `cli.js`) with `shell: false`; unverified `.cmd` launchers
+are still refused.
+
+The same npm-shim miss can appear for `pi` on Windows.
+
 ### Pi shows `hub:off`
 
 - Confirm the hub is reachable from the Pi terminal.
@@ -88,6 +115,19 @@ release asset through the authenticated `gh release download` flow in
 `node scripts/kxm.mjs` from a clone after `npm ci`. `npx kxm` and a
 global `git+https` npm install are not supported installation paths.
 
+For bash and zsh, `kxm completion install` can add the kxm bin directory to
+`PATH` in the shell rc file when it is missing; restart the shell afterwards.
+
+### Tab completion is not active
+
+Run `kxm completion install` for the detected shell, or pass
+`--shell bash|zsh|fish` explicitly. The install appends one guarded stanza to
+the shell rc file and is idempotent: rerunning never duplicates it. Fish needs
+no rc entry because fish auto-loads `~/.config/fish/completions`. After
+installing, start a new terminal or `source` the rc file. To inspect without
+writing, use `--dry-run`; to suppress the post-`kxm init` offer, set
+`KXM_SKIP_COMPLETION_PROMPT=1`.
+
 ### An expected peer is missing
 
 The two agents usually have different `KXM_PROJECT` values or one stopped sending heartbeats. Compare settings and check for an `agent_stale` event. Names and projects are case-sensitive for display; live-name uniqueness is case-insensitive.

package/docs/vnext/validation.md

@@ -22,6 +22,15 @@ The `schema` field is required. For agent, model, and workflow files, identity i
 the normalized filename without `.yaml`; an in-document identity field is
 forbidden.
 
+The shared implementation is `plugins/kxm/src/restricted-yaml.mjs`. Public
+`vnext-config` callers still receive `VnextConfigError` issue codes, paths, and
+messages.
+
+`schemas/policy-draft` (`kxm.model.v2`, `kxm.role.v2`) and
+`validatePolicyDraft` are non-authoritative scaffolding. They are not live
+registry identities, operator settings, or admission. Live model files remain
+`kxm.model.v1` under `schemas/vnext`.
+
 ## Validation pipeline
 
 ### 1. Parse validation

package/docs/webhook-workflows.md

@@ -21,7 +21,7 @@ The hub stores a SHA-256 payload hash and the rendered coordinator prompt, not t
 
 ## Configure the Jira example
 
-The included [`jira-development.json`](../.kxm/config/workflows/jira-development.json) workspace configuration models this path:
+The included [`jira-development.json`](../.kxm/workflows/default.yaml) workspace configuration models this path:
 
 1. Jira issue enters **In Progress**.
 2. Reproduce the defect and create deterministic evidence.
@@ -41,7 +41,7 @@ Load it without storing its secret in the JSON file:
 ```powershell
 $env:JIRA_WEBHOOK_SECRET = "replace-with-a-high-entropy-secret"
 $env:WORKFLOW_SIGNAL_SECRET = "replace-with-a-separate-callback-secret"
-$env:KXM_WEBHOOK_WORKFLOWS_FILE = ".kxm/config/workflows/jira-development.json"
+$env:KXM_WEBHOOK_WORKFLOWS_FILE = ".kxm/workflows/default.yaml"
 kxm hub start
 ```
 

package/examples/README.md

@@ -2,7 +2,7 @@
 
 These examples demonstrate the transport without requiring an AI model. Run them from the repository root after `npm ci`.
 
-The [`.kxm/config/workflows/jira-development.json`](../.kxm/config/workflows/jira-development.json) workspace configuration is a production-oriented definition for a long-lived coordinator. It covers reproduction, single-agent or three-agent planning, plan review, implementation, local and repository gates, documentation, push/watch retries, merge, Jira update, and continuous improvement. Follow [Webhook workflows](../docs/webhook-workflows.md) to configure it.
+The [`.kxm/workflows/default.yaml`](../.kxm/workflows/default.yaml) workspace configuration is a production-oriented definition for a long-lived coordinator. It covers reproduction, single-agent or three-agent planning, plan review, implementation, local and repository gates, documentation, push/watch retries, merge, Jira update, and continuous improvement. Follow [Webhook workflows](../docs/webhook-workflows.md) to configure it.
 
 The [`workflow-signal.ts`](workflow-signal.ts) sender demonstrates the signed callback that resumes a coordinator after CI, review, merge, or Jira work completes. The webhook guide documents its required environment and arguments.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kontextmind/kxm",
-  "version": "0.6.0",
+  "version": "0.7.4",
   "description": "KXM local-first multi-agent orchestration and operator dashboard",
   "type": "module",
   "author": "KontextMind",
@@ -38,8 +38,8 @@
     "test:simulations": "npm run build && node --disable-warning=ExperimentalWarning --experimental-strip-types --test --test-concurrency=4 test/simulations/*.test.ts",
     "test:complete": "npm run build && node --disable-warning=ExperimentalWarning --experimental-strip-types --test --test-concurrency=4 test/core/*.test.ts test/simulations/*.test.ts",
     "test": "npm run test:core",
-    "test:coverage:core": "npm run build && node --disable-warning=ExperimentalWarning --experimental-strip-types --test --test-concurrency=4 --experimental-test-coverage --test-coverage-lines=92 --test-coverage-branches=80 --test-coverage-functions=93 --test-coverage-include=plugins/kxm/src/**/*.ts --test-coverage-exclude=plugins/kxm/src/server.ts --test-coverage-exclude=plugins/kxm/src/mcp-server.ts test/core/*.test.ts",
-    "test:coverage:complete": "npm run build && node --disable-warning=ExperimentalWarning --experimental-strip-types --test --test-concurrency=4 --experimental-test-coverage --test-coverage-lines=93 --test-coverage-branches=80 --test-coverage-functions=93 --test-coverage-include=plugins/kxm/src/**/*.ts --test-coverage-exclude=plugins/kxm/src/server.ts --test-coverage-exclude=plugins/kxm/src/mcp-server.ts test/core/*.test.ts test/simulations/*.test.ts",
+    "test:coverage:core": "npm run build && node --disable-warning=ExperimentalWarning --experimental-strip-types --test --test-concurrency=4 --experimental-test-coverage --test-coverage-lines=91 --test-coverage-branches=80 --test-coverage-functions=92 --test-coverage-include=plugins/kxm/src/**/*.ts --test-coverage-exclude=plugins/kxm/src/server.ts --test-coverage-exclude=plugins/kxm/src/mcp-server.ts --test-coverage-exclude=plugins/kxm/src/vnext-runtime-supervisor.ts test/core/*.test.ts",
+    "test:coverage:complete": "npm run build && node --disable-warning=ExperimentalWarning --experimental-strip-types --test --test-concurrency=4 --experimental-test-coverage --test-coverage-lines=93 --test-coverage-branches=80 --test-coverage-functions=93 --test-coverage-include=plugins/kxm/src/**/*.ts --test-coverage-exclude=plugins/kxm/src/server.ts --test-coverage-exclude=plugins/kxm/src/mcp-server.ts --test-coverage-exclude=plugins/kxm/src/vnext-runtime-supervisor.ts test/core/*.test.ts test/simulations/*.test.ts",
     "test:coverage": "npm run test:coverage:core",
     "typecheck": "tsc --noEmit",
     "lint:docs": "markdownlint-cli2",
@@ -82,29 +82,27 @@
     }
   },
   "devDependencies": {
-    "@earendil-works/pi-coding-agent": "0.84.3",
+    "@earendil-works/pi-coding-agent": "0.85.1",
     "@modelcontextprotocol/sdk": "1.30.0",
-    "@types/node": "26.4.0",
+    "@types/node": "26.4.1",
     "ajv": "8.20.0",
     "commander": "15.0.0",
     "esbuild": "0.28.2",
     "markdownlint-cli2": "0.23.2",
-    "typebox": "1.3.19",
-    "typescript": "7.0.2",
-    "yaml": "2.9.0"
+    "tsx": "^4.23.13",
+    "typebox": "1.3.28",
+    "typescript": "7.0.2"
   },
   "files": [
     ".kxm/README.md",
     ".kxm/assets/README.md",
     ".kxm/assets/retrospectives/README.md",
-    ".kxm/config/README.md",
-    ".kxm/config/env.example",
-    ".kxm/config/update.example.yaml",
-    ".kxm/config/agents.json",
-    ".kxm/config/workflows/jira-development.json",
-    ".kxm/config/workflows/v04-dogfood.json",
-    ".kxm/config/workflows/fix.json",
-    ".kxm/config/workflows/provenance-quorum.json",
+    ".kxm/project.yaml",
+    ".kxm/gates.yaml",
+    ".kxm/producers.yaml",
+    ".kxm/agents/*.yaml",
+    ".kxm/roles/*.yaml",
+    ".kxm/workflows/*.yaml",
     ".claude-plugin",
     "plugins/kxm/.claude-plugin",
     "plugins/kxm/.mcp.json",
@@ -124,6 +122,7 @@
   ],
   "license": "MIT",
   "dependencies": {
-    "@earendil-works/pi-tui": "0.84.4"
+    "@earendil-works/pi-tui": "0.85.1",
+    "yaml": "^2.9.0"
   }
 }

package/plugins/kxm/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "kxm",
   "displayName": "KXM",
-  "version": "0.6.0",
+  "version": "0.7.4",
   "description": "Headless multi-agent orchestration, durable workflows, and a live operator dashboard for Pi and Claude Code",
   "author": {
     "name": "KontextMind",

package/plugins/kxm/README.md

@@ -39,7 +39,7 @@ Configure the hub URL, token, unique agent name, purpose, and project when promp
 | `kxm_workflow_record` | Capture a plan, decision, contradiction, error, or lesson |
 | `kxm_improvement_report` | Group learning evidence by improvement area |
 
-The bundled `kxm` skill teaches Claude when and how to use these tools safely.
+The bundled `kxm` skill teaches Claude when and how to use these tools safely. For the complete KXM Agent Skills suite covering all KXM commands, see the [Agent Skills documentation](../../docs/agent-skills.md).
 
 Signed webhooks can create durable workflows for long-lived Pi coordinators. See the repository's [Webhook workflows](../../docs/webhook-workflows.md) guide and Jira development example.