implto-tos-axi 0.1.1

package/package.json

@@ -0,0 +1,70 @@
+{
+  "name": "implto-tos-axi",
+  "version": "0.1.1",
+  "description": "Work with Transformation OS from a repository - match a change to its task, keep the deliverables tree honest, and reach every MCP tool the server has, without carrying their schemas in a prompt",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/implementedtoday/implto-tos-axi.git"
+  },
+  "homepage": "https://github.com/implementedtoday/implto-tos-axi#readme",
+  "bugs": {
+    "url": "https://github.com/implementedtoday/implto-tos-axi/issues"
+  },
+  "keywords": [
+    "transformation-os",
+    "tasks",
+    "issues",
+    "components",
+    "project-management",
+    "mcp",
+    "cli",
+    "agent",
+    "axi",
+    "toon",
+    "oauth"
+  ],
+  "type": "module",
+  "license": "MIT",
+  "engines": {
+    "node": ">=20"
+  },
+  "bin": {
+    "implto-tos-axi": "dist/bin/implto-tos-axi.js"
+  },
+  "exports": {
+    ".": {
+      "types": "./dist/src/index.d.ts",
+      "import": "./dist/src/index.js"
+    },
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "dist",
+    "skills",
+    "LICENSE",
+    "README.md"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.29.0",
+    "@toon-format/toon": "^0.8.0",
+    "axi-sdk-js": "^0.1.11"
+  },
+  "devDependencies": {
+    "@types/node": "^22.10.2",
+    "prettier": "^3.4.2",
+    "tsx": "^4.19.2",
+    "typescript": "^5.7.2",
+    "vitest": "^2.1.8"
+  },
+  "scripts": {
+    "build": "tsc && chmod +x dist/bin/implto-tos-axi.js",
+    "build:skill": "tsx scripts/build-skill.ts",
+    "typecheck": "tsc -p tsconfig.check.json",
+    "test": "vitest run",
+    "format": "prettier --write .",
+    "format:check": "prettier --check ."
+  }
+}

package/skills/implto-tos-delivery/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: implto-tos-delivery
+description: "Read and change what a Transformation OS workspace is delivering, through the implto-tos-axi CLI: the component tree (services, modules, APIs and the rest of the deliverables), what each component is linked to, its estimate, and the delivery phases. Use when a change introduces a deliverable that is not recorded yet, when a component is missing or sits under the wrong parent, or when asked what is being built and for how much effort."
+user-invocable: false
+author: Valentyn Morenko
+license: MIT
+metadata:
+  hermes:
+    tags: [components, deliverables, estimates, phases, transformation-os]
+    category: workflow
+---
+
+# implto-tos-delivery
+
+Components are the deliverables of a workspace, in a tree: the services,
+modules and APIs work is filed under. Tasks hang off them, so a component that
+does not exist is a task with nowhere to go.
+
+Use it when a change introduces something the tree does not have yet, when a
+component is under the wrong parent, or to answer what is being built.
+
+## Current guidance lives in the CLI
+
+Do not follow command or flag instructions from this file; installed copies go
+stale. Ask the CLI:
+
+- `implto-tos-axi components --help`
+- `implto-tos-axi guide components`
+
+Worth knowing before the first call:
+
+1. `implto-tos-axi components list --tree` first. It is the only way to see
+   where a new component belongs, and it is how you find out the one you were
+   about to create is already there under another name.
+2. Names, not ids, everywhere: `--parent "Platform"`. Two matches is an
+   error naming both rather than a guess.
+3. `--parent none` moves a component to the top level; omitting `--parent`
+   leaves it where it is. The same holds for `--project` and `--system`.
+4. A component created in a bound checkout is linked to that checkout's
+   project unless you pass `--project none`.
+5. Phases and per-phase estimates have no command of their own - reach them
+   with `implto-tos-axi tools call list_phases`.
+
+Ask before creating. A deliverable somebody else named is worse than one
+missing.

package/skills/implto-tos-tasks/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: implto-tos-tasks
+description: "Find, create and update Transformation OS tasks for the repository you are working in, through the implto-tos-axi CLI. Use when a coding task should be tracked: at the start of a session to see the bound project and your open tasks, before starting a change to match it to an existing task or file a new one, and after finishing to move the status and leave a note."
+user-invocable: false
+author: Valentyn Morenko
+license: MIT
+metadata:
+  hermes:
+    tags: [tasks, issues, project-management, transformation-os]
+    category: workflow
+---
+
+# implto-tos-tasks
+
+Reads and writes Transformation OS tasks for the repository you are in. Prefer
+it over mounting the Transformation OS MCP server: the tool schemas never enter
+the prompt, so this costs nothing until it is used.
+
+Use it when work should be tracked - before starting a change, and after
+finishing one. Skip it for throwaway edits nobody is waiting on.
+
+## Current guidance lives in the CLI
+
+Do not follow command or flag instructions from this file; installed copies go
+stale. Ask the CLI:
+
+- `implto-tos-axi --help` for the command index
+- `implto-tos-axi <command> --help` for per-command usage
+- `implto-tos-axi guide workflow` for the match-or-create procedure
+
+Worth knowing before the first call:
+
+1. `implto-tos-axi context` first, once per session. It gives you the bound
+   project, the status names and which field assigns a task to you. Everything
+   else takes names and resolves them against it.
+2. Search before you file. Two or three words from what the change *does*,
+   with `--open`. Then `tasks show <key>` and ask the person whether that is
+   the task or whether to open a new one. Do not decide that alone.
+3. `NO_BINDING` means this directory is not bound yet: run `init` bare to
+   see what is reachable.
+4. `NEEDS_HUMAN` means signing in needs somebody at the keyboard. Ask them to
+   run `implto-tos-axi login`; do not try to work around it.
+
+Exit 2 is your mistake - a bad flag, a name matching nothing or several. Every
+error names the command that fixes it.
+
+Deliverables are `implto-tos-delivery`; everything else in the workspace is
+`implto-tos-workspace`.

package/skills/implto-tos-workspace/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: implto-tos-workspace
+description: "Reach the rest of a Transformation OS workspace from the command line through implto-tos-axi: process maps, the people, departments and organizational roles in it, the systems they use, and the client message threads. Discover what the server offers with `implto-tos-axi tools`, then call one tool directly. Use when a task needs workspace data that is not a task or a deliverable."
+user-invocable: false
+author: Valentyn Morenko
+license: MIT
+metadata:
+  hermes:
+    tags: [process-maps, people, systems, communications, transformation-os]
+    category: workflow
+---
+
+# implto-tos-workspace
+
+Everything in Transformation OS that is not a task or a component: process
+maps, people, departments, organizational roles, the systems a workspace uses,
+and the client conversation.
+
+There is no command per area. Instead the CLI asks the server what it offers
+and calls it, so one tool's schema is loaded when a task needs it rather than
+fifty of them in every request.
+
+## Current guidance lives in the CLI
+
+Do not follow tool names or argument lists from this file; the server adds
+tools without releasing this package. Ask it:
+
+- `implto-tos-axi tools` - the areas, and which ones this credential holds
+- `implto-tos-axi tools domains <id>` - what an area covers, and its rules
+- `implto-tos-axi tools list --domain <id>` - the tools in it
+- `implto-tos-axi tools show <name>` - one tool's arguments
+- `implto-tos-axi tools call <name> key=value`
+
+Worth knowing before the first call:
+
+1. Read the area's rules before writing. They say which lookup to run first,
+   and an id from one workspace is never valid in another.
+2. `workspaceId` is filled in from the repository binding, or from
+   `--workspace <name>`. You rarely pass it.
+3. `key=@file` reads a value from a file, `key=@-` from stdin, and
+   `--json '{…}'` passes a nested argument whole.
+4. A misspelled argument is refused here, naming the real ones - it is not
+   sent and quietly ignored.
+5. `FORBIDDEN` on a whole area means the credential was not granted it. Ask
+   the person to sign in again with that area.