v1.1.1 · on npmOpen-source · MIT License

OpenCode Orchestrator Kit

An OpenCode plugin that sends each coding task to a specialist on the cheapest model that can do it. You keep a resumable plan, a smaller context, and a router that never edits your application code — 16 core agents.

{ "package": "opencode-orchestrator-kit", "options": { "preset": "generic", "withExtras": false } }

npm packagev1.1.1 releaseChangelog

How it works

Four phases from repo bootstrap to a verified checkpoint.

Bootstrap

The profiler fingerprints the repo and scaffolds .context/ and plan/.

Route

The orchestrator reads the request and picks the specialist that should do it.

Delegate

That specialist gets one precise 9-section task spec.

Verify & checkpoint

Results are checked, progress.md is updated, and the plan advances one phase at a time.

v1.1.1

What's new in 1.0

The kit is now an OpenCode 2 plugin, published on npm.

Install from npm

opencode-orchestrator-kit is the OpenCode 2 plugin. Add the package to the plugins array and the roster, commands, and skills register at runtime.

A plan board with an owner

plan-writer is the only agent that creates or moves plan files. On OpenCode 2 it calls the native plan_board tool; the v1 installer falls back to scripts/plan-board.py.

Four session commands

Start a session, recall a comprehension review, opt into research recording, and close the session without starting new work.

Design rules on an empty repo

The first run looks for a design-rules artifact. On a new repository the profiler asks for the goal and seeds one. Existing artifacts are reported, not overwritten.

Companion kits stay optional

This kit runs on its own. It does not fetch or pin another repository. A companion may install its own skills and commands where OpenCode already looks. web-* is a reserved prefix for a web-stack skill pack. A web-kit is one example of that shape. This package runs without a companion repository.

Extras are opt-in

pc-doctor and writer are not part of the default roster. Set withExtras to true, or on the legacy installer pass --with-extras.

Commands

The plugin registers these four commands. A companion kit registers its own commands separately.

/start-session

Start the session by having the orchestrator bootstrap the repo profile and load the session memory.

/quick

Switch this session to the slim orchestrator for small tasks — one delegation, no plan board, no session memory.

/recall

Re-activate a past comprehension session for a plan via a strict read-only diagnostic and comprehension re-verification flow.

/research-mode

Explicitly activate or deactivate research mode (opt-in A/B crossover + event recording).

/close-session

Close the session by having the orchestrator flush pending session-memory updates and shut down cleanly without starting new work.

16 core agents

Agent roster

16 agents ship in agents/. Badges come from each file's permission block. Opt-in extras live in extras/ and stay off unless you ask for them.

Core routing

Installed by default. The primary agent only routes.

scoped write

orchestratorrouter

Coordination agent that breaks work into steps, assigns each step to the right specialist, and manages parallel or sequential execution.

scoped write

orchestrator-quickrouter

Slim orchestrator for small tasks — one delegation, kit-grade verification, no plan board and no session memory.

scoped write

profiler

>-

read-only

explorer

Fast codebase explorer that finds files, traces symbols, and answers structure questions at a chosen depth.

read-only

oracle

Read-only technical advisor that gives one well-reasoned recommendation for architecture, design, or strategy.

scoped write

planner

>-

Core delivery

Installed by default. Implementation, tests, review, and the plan board.

writes

developer-fixer

>-

edit: ask

test-engineer

>-

read-only

code-reviewer

>-

read-only

security

>-

read-only

comprehension-coach

>-

scoped write

plan-writer

>-

Operations helpers

Installed by default, and routed only when a matching build, npm, or deploy failure shows up.

edit: ask

build-helper

>-

edit: ask

npm-helper

>-

edit: ask

deploy-helper

>-

Docs lookup

Installed by default, and routed only for remote documentation lookups.

read-only

librarian

>-

Opt-in extras

2 agents in extras/. Set withExtras to true on the plugin, or pass --with-extras to the legacy installer.

edit: ask

pc-doctor

>-

writes

writer

Technical writer that produces clear, verified documentation for READMEs, APIs, architecture, and user guides.

Quickstart

On OpenCode 2, install the npm package. Git, a local directory, the legacy installer, and OpenCode Studio are the other paths.

Primary install on OpenCode 2. Add the npm package to the plugins array in opencode.json or opencode.jsonc. Nothing is copied into .opencode/.

{
  "$schema": "https://opencode.ai/config.json",
  "plugins": [
    {
      "package": "opencode-orchestrator-kit",
      "options": { "preset": "generic", "withExtras": false },
    },
  ],
}

Peer dependency: @opencode/plugin ^2.1.0. preset selects the tier mapping (generic is the one you edit). withExtras defaults to false, so pc-doctor and writer stay off until you opt in.

Why this exists

Spend the strong model on the steps that need it, and keep the rest of the session cheap enough to finish.

The router stays out of your code

The orchestrator classifies, delegates, and checkpoints. A routing mistake cannot silently edit the repository.

Match the model to the step

Exploration and triage run on cheaper models. Stronger models are reserved for design, implementation, and review.

The plan outlives the chat

Work sits on a file board and session memory stays small, so the next session can resume without replaying the whole conversation.