ktg-plugin-marketplace

Open-source Claude Code plugins. Currently one: Voyage. More are added when they are good enough.

Built for my own Claude Code workflow and shared openly for anyone who finds them useful. Solo-maintained, AI-assisted, fork-and-own. Issues are welcome as signals; pull requests are not accepted. See GOVERNANCE.md for what upstream provides and how this is meant to be used.

All code here is generated by Claude Code through a dialog-based process: I direct, review, test, and validate; Claude writes. Treat the plugins as AI-authored, human-curated.

Install

claude plugin marketplace add https://git.fromaitochitta.com/open/ktg-plugin-marketplace.git

Then open Claude Code and type /plugin to browse and install — the command above only registers the marketplace, it installs nothing.

Each plugin keeps its own full README and CHANGELOG; this page is just the catalog.

Staying up to date

Auto-update is off by default for this marketplace. claude plugin marketplace add records no autoUpdate key, and Claude Code only defaults it on for Anthropic's own catalogs — so a release published here does not reach an already-registered machine on its own.

Pull updates by hand:

claude plugin marketplace update ktg-plugin-marketplace   # refresh the catalog
claude plugin update <plugin>                             # update one installed plugin (restart to apply)

Or turn auto-update on once, by declaring the marketplace in your user settings (~/.claude/settings.json). This is the entry marketplace add already writes, plus autoUpdate:

{
  "extraKnownMarketplaces": {
    "ktg-plugin-marketplace": {
      "source": {
        "source": "git",
        "url": "https://git.fromaitochitta.com/open/ktg-plugin-marketplace.git"
      },
      "autoUpdate": true
    }
  }
}

Claude Code then refreshes this marketplace and its installed plugins on startup.

Measured on Claude Code 2.1.260 in an isolated CLAUDE_CONFIG_DIR profile: a fresh marketplace add writes the entry above without autoUpdate; setting the key to true propagates to plugins/known_marketplaces.json on the next start, and false propagates too.

Non-goals

• Not a host for plugin source or issues. This repository holds the marketplace manifest and this catalog page. Code, issues and releases live in each plugin's own repository, linked from its entry below.
• Not a third-party registry. Only plugins maintained here are listed. There is no submission process.
• No pull requests. Issues are welcome as signals; PRs are not accepted. See GOVERNANCE.md for the reasoning and the fork-and-own model.
• No support commitment. Bug fixes are best-effort, breaking changes happen and are documented in each plugin's CHANGELOG. Version-pin if you need stability.

---

Plugins

Voyage v6.5.0

A six-command planning pipeline with specialized agent swarms, adversarial review, and zero-friction multi-session resumption. Renamed from ultraplan-local//ultra*-local to avoid collision with Anthropic's /ultraplan and /ultrareview. No cloud dependency.

• /trekbrief — capture intent through a quality-gated interview; emits a reviewable brief
• /trekresearch — deep multi-source research with triangulation and confidence ratings
• /trekplan — transform the brief into an executable, manifest-verified plan
• /trekexecute — disciplined execution with independent audit and bounded failure recovery
• /trekreview — independent post-hoc review; severity-tagged findings feed back into planning
• /trekcontinue — resume the next session from saved state in one command

Per-phase effort and model dialog; /trekbrief, /trekplan, and /trekreview render an operator-annotation HTML view you can mark up and copy back into Claude.

24 agents · 6 commands (+1 helper) · 7 hooks · 832 tests · Full documentation → · Migration guide

---

Tests

This repository's own gates — version consistency between each plugin entry and the tag it pins, catalog-to-plugin stat mirroring, OKF parity, and the navigation goldens — are covered by tests:

node --test scripts/*.test.mjs

The test files under docs/marketplace-polyrepo-migration/ belong to the one-off migration that split the former monorepo into per-plugin repositories. They are kept as a record of that migration and are not part of the suite above.

---

License

MIT