Skip to content
Back to search

orgtomo

MarketplaceWorks with Claude CodeGitHub

A team of Claude Code agents that takes a Salesforce ticket from understanding to a verified deploy pack, with proof at every step.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/khadda-ai--orgtomo/badge.svg)](/listings/khadda-ai--orgtomo)

HTML

<a href="/listings/khadda-ai--orgtomo"><img src="/api/listings/khadda-ai--orgtomo/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

npm install -g github:khadda-ai/orgtomo

mkdir my-company && cd my-company
orgtomo setup            # asks for your orgs, deploy tools and allowed test data
orgtomo doctor --orgs    # checks the CLI, each org, and whether it is really a sandbox

orgtomo brain sync uat   # build the org map
orgtomo discover run uat --retrieve   # optional: study how the business uses the org
orgtomo ui               # review agents, safety and features, browse the org map

Install the three plugins for this folder only, so that they load here and nowhere else:

claude plugin marketplace add khadda-ai/orgtomo
claude plugin install orgtomo@orgtomo --scope project
claude plugin install salesforce-development@orgtomo --scope project
claude plugin install salesforce-code-quality@orgtomo --scope project

Then start a session with the Lead and give it a ticket:

orgtomo start
/orgtomo:ping
/orgtomo:ticket ABC-123

Full walkthrough: [docs/SETUP.md](docs/SETUP.md).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 39 lines
  1. {
  2. "name": "orgtomo",
  3. "owner": {
  4. "name": "Khadda AI Labs"
  5. },
  6. "metadata": {
  7. "description": "Orgtomo and the Salesforce plugins it builds on. forcedotcom/sf-skills changes often; the two Salesforce plugins are pinned to one commit so that agent behaviour changes only when a maintainer moves the pin (see sf-skills.lock).",
  8. "version": "0.2.0"
  9. },
  10. "plugins": [
  11. {
  12. "name": "orgtomo",
  13. "description": "The Orgtomo team: commands, guards and the engine.",
  14. "source": "./"
  15. },
  16. {
  17. "name": "salesforce-development",
  18. "description": "Salesforce skills, LSP and metadata tools from forcedotcom/sf-skills, pinned to commit 788b83fb (plugin 2.8.0).",
  19. "version": "2.8.0",
  20. "source": {
  21. "source": "git-subdir",
  22. "url": "https://github.com/forcedotcom/sf-skills.git",
  23. "path": "plugins/builder/salesforce-development",
  24. "sha": "788b83fb9f5effb4f1548e3090df415704d3ec64"
  25. }
  26. },
  27. {
  28. "name": "salesforce-code-quality",
  29. "description": "Code Analyzer skills and the architecture review agent from forcedotcom/sf-skills, pinned to commit 788b83fb (plugin 0.2.0).",
  30. "version": "0.2.0",
  31. "source": {
  32. "source": "git-subdir",
  33. "url": "https://github.com/forcedotcom/sf-skills.git",
  34. "path": "plugins/builder/salesforce-code-quality",
  35. "sha": "788b83fb9f5effb4f1548e3090df415704d3ec64"
  36. }
  37. }
  38. ]
  39. }
README.md · README · 173 lines
  1. # Orgtomo
  2. A team of Claude Code agents that takes a Salesforce ticket from "what is being asked" to a verified deploy pack, with proof at every step.
  3. [![CI](https://github.com/khadda-ai/orgtomo/actions/workflows/ci.yml/badge.svg)](https://github.com/khadda-ai/orgtomo/actions/workflows/ci.yml)
  4. [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
  5. *Org* + *tomo* (友, Japanese for friend, companion).
  6. ## What it is
  7. Orgtomo runs inside [Claude Code](https://code.claude.com/docs). You give it a ticket key. A lead agent hands the work to specialists, one stage at a time, and an engine decides after each stage whether the result is good enough to continue.
  8. It is built for Salesforce developers, admins and consultants who already do this work with an AI assistant by hand: paste the ticket, ask for an explanation, ask for a reproduction, ask for a plan, build, test, write the update. Orgtomo makes that sequence a system, and adds the parts that are easy to skip when doing it by hand.
  9. **Nothing is guessed.** Every claim an agent makes must cite evidence that the engine itself recorded: a query result, a test run, a deploy, a fresh fact from the org map, or a sentence from official Salesforce documentation. Wording such as "probably" fails a gate.
  10. **The Lead does not trust reports.** After a stage passes its gates, the Lead re-runs the proof of one claim and compares.
  11. **Production is read-only.** Reads are masked. There is no setting that changes this.
  12. **Humans deploy.** Agents build and test in your dev sandbox. For every other org, Orgtomo prepares a deploy pack for your tool (Blue Canvas, change sets, Git and the CLI, or a generic checklist), waits for you, then checks that the org matches what was built.
  13. **Test data is safe.** Only the e-mail addresses and phone numbers you allow may appear in test records, scripts, browser input and drafts. In the default mode, agents write data only while the sandbox cannot send e-mail.
  14. **It learns from what really happened.** Failed gates, rejected plans, reviewer findings and your own feedback are recorded as observations. Lessons must cite them. Approved lessons are loaded by the agent they concern.
  15. ## The team
  16. | Agent | Role |
  17. |---|---|
  18. | Tomo Lead | Architect and manager. Delegates, verifies, reports. Never builds. |
  19. | Analyst | Business analyst, functional consultant and product owner: plain and technical understanding, acceptance criteria, examples. |
  20. | Reproducer | Proves a bug with data in a sandbox. Never by reading code. |
  21. | Planner | Smallest correct design, grounded in the org map and official documentation. |
  22. | Builder | Implements the approved plan in the build org: backup first, your naming and comment style. |
  23. | Tester | Tests every criterion with proof, reruns the reproduction, bulk and regression. |
  24. | Reviewer | Independent review against a rubric, on a different model from the Builder. |
  25. | Cartographer, Baseline, Scribe, Coach, Notetaker | Org map, before-state, message drafts, lessons, meeting notes. Optional ones have a switch. |
  26. ## How a ticket moves
  27. ```mermaid
  28. flowchart LR
  29. open --> understand --> repro --> plan --> build --> test --> review --> handoff --> close --> done
  30. test -. "fails: back to plan (max 2 loops, then stop)" .-> plan
  31. review -. "changes requested" .-> plan
  32. plan -- "human approves" --> build
  33. review -- "human approves" --> handoff
  34. handoff -- "human deploys, per org" --> handoff
  35. ```
  36. Stages, gates and contracts are data (`spec/stages.yaml`, `spec/gates.yaml`, `spec/schemas/`). The engine interprets them.
  37. ## Requirements
  38. - Claude Code
  39. - Node.js 20 or newer
  40. - Salesforce CLI (`sf`), logged in to each org under an alias
  41. - Optional: [Obsidian](https://obsidian.md) to browse the vault (the control panel shows the org map too); a tracker connector (Atlassian by default); the Playwright MCP server for browser steps
  42. Orgtomo has no runtime dependencies to install. The one third-party library it uses is vendored.
  43. ## Quick start
  44. ```bash
  45. npm install -g github:khadda-ai/orgtomo
  46. mkdir my-company && cd my-company
  47. orgtomo setup # asks for your orgs, deploy tools and allowed test data
  48. orgtomo doctor --orgs # checks the CLI, each org, and whether it is really a sandbox
  49. orgtomo brain sync uat # build the org map
  50. orgtomo discover run uat --retrieve # optional: study how the business uses the org
  51. orgtomo ui # review agents, safety and features, browse the org map
  52. ```
  53. Install the three plugins for this folder only, so that they load here and nowhere else:
  54. ```bash
  55. claude plugin marketplace add khadda-ai/orgtomo
  56. claude plugin install orgtomo@orgtomo --scope project
  57. claude plugin install salesforce-development@orgtomo --scope project
  58. claude plugin install salesforce-code-quality@orgtomo --scope project
  59. ```
  60. Then start a session with the Lead and give it a ticket:
  61. ```bash
  62. orgtomo start
  63. ```
  64. ```
  65. /orgtomo:ping
  66. /orgtomo:ticket ABC-123
  67. ```
  68. Full walkthrough: [docs/SETUP.md](docs/SETUP.md).
  69. ## What you type
  70. | You type | What happens |
  71. |---|---|
  72. | `/orgtomo:ticket ABC-123` | The team starts or continues the ticket |
  73. | `/orgtomo:approve` / `/orgtomo:reject <reason>` | Your decision at a gate |
  74. | `/orgtomo:answer Q1 <text>` | Answer a blocking question |
  75. | `/orgtomo:deployed uat` | You finished a deploy; parity check and retest follow |
  76. | `/orgtomo:feedback bad planner <what you saw>` | Recorded as evidence for lessons |
  77. | `/orgtomo:rule builder <rule>` | A rule in your words; applies at once |
  78. | `/orgtomo:models planner opus xhigh` | Model and effort per agent |
  79. | `/orgtomo:restore ABC-123` | Put the backed-up versions back into the build org |
  80. | `/orgtomo:status`, `/orgtomo:lessons`, `/orgtomo:brain`, `/orgtomo:doctor` | Look around |
  81. All commands: [docs/COMMANDS.md](docs/COMMANDS.md).
  82. ## Configuration
  83. Everything about your setup lives in `orgtomo.config/` in your workspace. Agents cannot write there.
  84. | File | Holds |
  85. |---|---|
  86. | `orgs.yaml` | Your orgs, their CLI aliases and roles (build, test, reference, production) |
  87. | `pipeline.yaml` | Build org, deploy targets and tools, loop limit, autonomy, lite path |
  88. | `safety.yaml` | E-mail mode, allowed test addresses and numbers, masking, browser rules |
  89. | `agents.yaml` | Model, effort and on/off per agent |
  90. | `features.yaml` | Lite path, self-learning, meetings, people profiles, Flow generator, telemetry |
  91. | `conventions.yaml` | Your naming, comment and format rules, and forbidden patterns |
  92. | `capabilities.yaml` | Which tool provides which capability; add your own MCP servers here |
  93. Change them in the files, in the control panel (`orgtomo ui`), or with the slash commands. Details: [docs/CONFIGURATION.md](docs/CONFIGURATION.md).
  94. ## The vault
  95. Knowledge is kept as Markdown in `vault/`, which opens as an Obsidian vault:
  96. - `orgs/<org>/`: the org map. One generated note per component with what it uses and what uses it, a hub page per object, a "what runs on this object" note in save order, and a canvas map.
  97. - `orgs/<org>/business/`: how the business uses the org (optional). Areas and their objects, one process note per area with a fact behind every statement, and the questions only a person can answer.
  98. - `tickets/<KEY>/`: every stage output, gate report, evidence and deploy pack.
  99. - `learning/`: observations and lessons.
  100. - `meetings/`, `people/`: optional features.
  101. ## Built on
  102. - [forcedotcom/sf-skills](https://github.com/forcedotcom/sf-skills) (Apache-2.0) for Salesforce skills, the Apex and SOQL language server and Code Analyzer. Orgtomo installs it as separate plugins pinned to one commit (`sf-skills.lock`); nothing from it is copied into this repository.
  103. - The Salesforce CLI for all org access.
  104. - [Playwright MCP](https://github.com/microsoft/playwright-mcp) for browser steps (optional).
  105. ## Status
  106. Version 0.2.0. Every released version keeps its own branch (`release/v0.1.0`, `release/v0.2.0`), so any of them can be installed by name. The engine, guards and gates are covered by an offline test suite that includes a complete ticket and adversarial cases. What has and has not yet been exercised against live orgs and a live Claude Code session is listed plainly in [docs/VERIFICATION.md](docs/VERIFICATION.md). Read it before relying on Orgtomo for real work.
  107. ## Documentation
  108. - [Setup](docs/SETUP.md)
  109. - [Architecture](docs/ARCHITECTURE.md)
  110. - [Safety model and its limits](docs/SAFETY.md)
  111. - [Agents](docs/AGENTS.md)
  112. - [Knowledge: org map, learning, meetings, people](docs/KNOWLEDGE.md)
  113. - [Configuration](docs/CONFIGURATION.md)
  114. - [Commands](docs/COMMANDS.md)
  115. - [Verification status](docs/VERIFICATION.md)
  116. ## Contributing
  117. See [CONTRIBUTING.md](CONTRIBUTING.md). Pull requests target `develop`.
  118. ## Security
  119. See [SECURITY.md](SECURITY.md) for how to report a vulnerability, and [docs/SAFETY.md](docs/SAFETY.md) for what the guards do and do not protect against.
  120. ## License
  121. MIT. Copyright (c) 2026 Khadda AI Labs. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.