agent-orchestra

Agent Orchestra

⚠️ GitHub Copilot / VS Code support is frozen and retiring after 2026-08-31. Claude Code is the actively supported path. See COPILOT-DEPRECATION.md for details and the reach-out channel if you depend on Copilot support.

A multi-agent workflow system that orchestrates AI-assisted software development through specialized Claude Code agents. (GitHub Copilot/VS Code: frozen and retiring after 2026-08-31 — see COPILOT-DEPRECATION.md)

Renamed from copilot-orchestra in v2.0.0. See the migration section below for the one-time steps to switch over.

Install as Plugin (VS Code 1.110+)

⚠️ Copilot / VS Code support is frozen and retiring after 2026-08-31. Claude Code is the actively supported path — see Install as Plugin (Claude Code) below. If you depend on the Copilot/VS Code surface, start a GitHub Discussion before the deadline. See COPILOT-DEPRECATION.md for details. Experimental: Agent plugins are available in VS Code 1.110 as an experimental feature. Plugin distribution is the fastest way to get started with no cloning required.

Quick Setup (Plugin)

1. Enable plugins — Add to VS Code user settings (Ctrl+Shift+P → "Open User Settings (JSON)"):

   {
     "chat.plugins.enabled": true,
     "chat.plugins.marketplaces": ["Grimblaz/agent-orchestra"]
   }
   

2. Install — In the Extensions view (Ctrl+Shift+X), search @agentPlugins agent-orchestra and install.

3. Use — The 16-agent payload and shared skill library are immediately available in VS Code Chat.

What's included in the repo plugin payload: 16 agents, the shared skill library, and 16 command files under commands/ (/code-conductor, /design, /experience, /orchestrate, /spine-run, /orchestra:spine, /plan, /polish, /raw, /review-github, /setup-references, /orchestra:review, /orchestra:review-lite, /orchestra:review-prosecute, /orchestra:review-defend, /orchestra:review-judge). VS Code currently ignores the plugin commands field; Claude Code and CLI consumers use it.

What requires clone/fork: Instruction files (.github/instructions/) and project templates are not distributed via the plugin — they are auto-discovered by VS Code when you clone or fork the repo. Plugin-distributed hooks are also not active when you only point VS Code at a clone via chat.agentFilesLocations; deterministic SessionStart cleanup and Claude PostToolUse release-hygiene prompts require an actual plugin install.

Install as Plugin (Claude Code)

Claude Code loads agents and skills from .claude-plugin/plugin.json. Install via the built-in marketplace commands:

/plugin marketplace add Grimblaz/agent-orchestra
/plugin install agent-orchestra@agent-orchestra

All 16 agents and the shared skill library are immediately available. The marketplace command registers the source; the install command pulls the plugin into Claude Code's cache. See Documents/Decisions/0002-claude-code-plugin-schema.md for the schema rationale (agents uses an explicit registration whitelist; skills auto-discovers).

Path resolution for downstream consumers

This is zero-config for consumer repositories: after marketplace registration and plugin install, Claude Code loads the shared agent bodies and skills from its plugin cache. The repository using the plugin does not need a local agents/ directory.

See Documents/Design/hub-artifact-paths-audit.md for the full hub artifact path catalog.

For what's included in the plugin payload vs. what requires clone/fork, see the Install as Plugin (Claude Code) section above.

Related: see the Releases section in CLAUDE.md for cache invalidation behavior and the audit doc's How to Detect Staleness section for drift detection.

See also: CUSTOMIZATION.md > Script portability for plugin users.

The plugin payload includes all 16 shared agent definitions and the shared skill library. The Claude-specific command and specialist surface is outlined below.

Upstream Agents In Claude Code

The three upstream agents are first-class Claude Code citizens: