Add Conductor output (#44)

chubes4 · web-flow · commit 3573e20b3d36 · 2026-06-11T21:49:34.000-04:00
diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 Shared source for WordPress-focused agent skills and plugin packaging.
 
-This repo currently packages shared skills and setup files for Amp, Cline, Codex, Claude Code, Cursor, Continue, Devin CLI, Factory Droid, GitHub Copilot, Gemini, Junie, Kilo Code, Pi, Qodo, Roo Code, Windsurf/Cascade, Aider, and Zed as separate outputs:
+This repo currently packages shared skills and setup files for Amp, Cline, Codex, Claude Code, Conductor, Cursor, Continue, Devin CLI, Factory Droid, GitHub Copilot, Gemini, Junie, Kilo Code, Pi, Qodo, Roo Code, Windsurf/Cascade, Aider, and Zed as separate outputs:
 
 - prefers the WordPress Studio MCP server for site management, screenshots, and block validation
 - falls back to the Studio CLI through a shared Studio skill when MCP is unavailable
@@ -20,6 +20,7 @@ This repo currently packages shared skills and setup files for Amp, Cline, Codex
 - includes Devin CLI project config, rules, and skills under Devin's documented `.devin/` surfaces
 - adds Cline workspace rules, skills, MCP settings, and Cline plugin-surface documentation from official Cline docs
 - adds a Pi skills package using Pi's official package manifest and Agent Skills support
+- includes Conductor repository settings and guidance for running the existing Claude Code, Codex, and Cursor outputs in isolated Conductor workspaces
 - adds Roo Code workspace rules and project MCP config without introducing a Roo-specific backend service
 - adds a Qodo `AGENTS.md` workspace package and documents Qodo's manual MCP setup path from official Qodo docs
 - adds Zed project instructions, project-local skills, and project settings for MCP without introducing a Zed-specific backend service
@@ -137,6 +138,15 @@ claude --plugin-dir ./plugins/claude-code
    - running an audit request
 6. For workflow telemetry coverage, make sure the generated `wordpress-telemetry` MCP server starts alongside `wordpress-studio`.
 
+### Test in Conductor
+
+1. Review the generated Conductor output in `./plugins/conductor`.
+2. Confirm the generated repository settings exist at `plugins/conductor/.conductor/settings.toml`.
+3. Confirm `plugins/conductor/README.md` documents why this output uses `.conductor/settings.toml` instead of legacy `conductor.json`.
+4. Confirm the README points Conductor MCP setup back to the existing Claude Code, Codex, and Cursor MCP configs instead of generating a Conductor-only MCP file.
+5. In Conductor, open a workspace and use the generated settings as the shared repository script layer when the package workflow should run `pnpm install`, `pnpm build`, and `pnpm verify`.
+6. Use Conductor's MCP/provider settings or Sync Agent Configs to make the existing `wordpress-studio` and `wordpress-telemetry` MCP servers available to the agents you run in Conductor.
+
 ### Test in Gemini
 
 1. Copy or reference `./plugins/gemini` as the Gemini project context directory.
@@ -310,6 +320,7 @@ pi install ./plugins/pi
 - A bundled standalone telemetry MCP server built from repo-local Node dependencies
 - Codex packaging output in `plugins/codex/`
 - Claude Code packaging output in `plugins/claude-code/`
+- Conductor setup output in `plugins/conductor/`
 - Cursor packaging output in `plugins/cursor/`
 - Continue setup output in `plugins/continue/`
 - Factory Droid marketplace output in `plugins/factory/`
@@ -535,6 +546,19 @@ Official Devin references:
 - MCP configuration: https://docs.devin.ai/cli/extensibility/mcp/configuration.md
 - Configuration files: https://docs.devin.ai/cli/extensibility/configuration.md
 
+The Conductor setup output is generated to:
+
+```text
+plugins/conductor/
+```
+
+That folder currently contains:
+
+- `.conductor/settings.toml`
+- `README.md`
+
+The generated Conductor settings use the current `.conductor/settings.toml` repository settings format for shared setup and run scripts. Conductor MCP support stays in Conductor's app/provider settings and in the existing Claude Code, Codex, and Cursor MCP configs; this output intentionally does not generate legacy `conductor.json` or a Conductor-only MCP file.
+
 The generated Copilot MCP config launches both `studio mcp` and the bundled `wordpress-telemetry` MCP server through VS Code's MCP configuration.
 
 The Gemini plugin is generated to:
diff --git a/plugins/conductor/.conductor/settings.toml b/plugins/conductor/.conductor/settings.toml
@@ -0,0 +1,6 @@
+"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"
+
+[scripts]
+setup = "pnpm install"
+run = "pnpm build && pnpm verify"
+run_mode = "concurrent"
diff --git a/plugins/conductor/README.md b/plugins/conductor/README.md
@@ -0,0 +1,65 @@
+# WordPress.com for Conductor
+
+This output packages Conductor repository settings and guidance for using the shared Build with WordPress agent outputs inside Conductor workspaces.
+
+Conductor is a workspace layer for parallel Claude Code, Codex, and Cursor agents. It creates isolated Git worktrees, runs setup and run scripts from each workspace, and then helps review, open PRs, and archive finished branches.
+
+## Generated files
+
+- `.conductor/settings.toml` configures shared Conductor repository scripts.
+- `README.md` documents how Conductor should use the existing Claude Code, Codex, and Cursor outputs from this repository.
+
+## Setup
+
+1. Install Conductor for macOS from https://www.conductor.build/.
+2. Open the repository you want Conductor to manage.
+3. Copy this output's `.conductor/settings.toml` into the repository root when the Build with WordPress package scripts are the workflow you want new Conductor workspaces to share.
+4. Install or sync the underlying agent configs for the agents you plan to run:
+   - Claude Code: use `plugins/claude-code/`.
+   - Codex: use `plugins/codex/`.
+   - Cursor: use `plugins/cursor/`.
+5. In Conductor, use Sync Agent Configs or the agent/provider settings to make the same MCP servers available to Claude Code, Codex, and Cursor.
+
+## Scripts
+
+Current Conductor docs recommend committed repository settings in `.conductor/settings.toml` for shared setup and run scripts. Legacy `conductor.json` is not generated because current docs mark it as legacy and Conductor ignores repo-level `conductor.json` once `.conductor/settings.toml` exists.
+
+The generated settings use:
+
+```toml
+"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"
+
+[scripts]
+setup = "pnpm install"
+run = "pnpm build && pnpm verify"
+run_mode = "concurrent"
+```
+
+Adjust `scripts.setup` and `scripts.run` for repositories that consume these WordPress.com agent files instead of developing this package directly. Use `$CONDUCTOR_PORT` in run scripts when a workspace starts a local web server.
+
+## MCP support
+
+Conductor supports MCP servers through the app's MCP/provider configuration and can sync agent configs between Claude Code and Codex. The current repository settings schema documents scripts, prompts, environment variables, providers, and Git behavior, but it does not define a repository-level MCP server table.
+
+For that reason this output does not invent a Conductor-specific MCP file. Use the existing MCP configs generated for the underlying agents:
+
+- Claude Code: `plugins/claude-code/.mcp.json`
+- Codex: `plugins/codex/plugins/wordpress-studio/.mcp.json`
+- Cursor: `plugins/cursor/mcp.json`
+
+Those configs launch the shared `studio mcp` server plus the bundled `wordpress-telemetry` server. Conductor's MCP support and Sync Agent Configs should point at the same shared substrate instead of adding another WordPress.com backend.
+
+## Message queues
+
+Conductor message queues are a native composer/workspace feature. They do not require generated files in this package. Queue multiple prompts in Conductor when a workspace needs ordered follow-up work; keep durable WordPress.com workflow guidance in the underlying agent outputs and shared skills.
+
+## Source links
+
+- Product overview: https://www.conductor.build/
+- Workflow and workspaces: https://www.conductor.build/docs/concepts/workflow and https://www.conductor.build/docs/concepts/workspaces-and-branches
+- Scripts and repository settings: https://www.conductor.build/docs/reference/scripts and https://www.conductor.build/docs/reference/settings
+- Settings reference: https://www.conductor.build/docs/reference/settings/reference
+- Legacy conductor.json: https://www.conductor.build/docs/reference/conductor-json
+- MCPs and message queues changelog: https://www.conductor.build/changelog/0.1.0-mcps-message-queues
+- Repo settings migration changelog: https://www.conductor.build/changelog/0.62.0-repo-settings-browser-preview
+- Sync agent configs changelog: https://www.conductor.build/changelog/0.57.0-sync-agent-configs
diff --git a/scripts/build-plugins.mjs b/scripts/build-plugins.mjs
@@ -20,6 +20,7 @@ const cursorPluginDisplayName = pluginDisplayName;
 const continueOutputDir = path.join(pluginsDir, "continue");
 const factoryOutputDir = path.join(pluginsDir, "factory");
 const factoryPluginDir = path.join(factoryOutputDir, "plugins", pluginName);
+const conductorOutputDir = path.join(pluginsDir, "conductor");
 const geminiDisplayName = "WordPress.com";
 const qodoPluginDir = path.join(pluginsDir, "qodo");
 
@@ -641,6 +642,85 @@ mcpServers:
 `;
 }
 
+function buildConductorSettings() {
+  return `"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"
+
+[scripts]
+setup = "pnpm install"
+run = "pnpm build && pnpm verify"
+run_mode = "concurrent"
+`;
+}
+
+function buildConductorReadme() {
+  return `# WordPress.com for Conductor
+
+This output packages Conductor repository settings and guidance for using the shared Build with WordPress agent outputs inside Conductor workspaces.
+
+Conductor is a workspace layer for parallel Claude Code, Codex, and Cursor agents. It creates isolated Git worktrees, runs setup and run scripts from each workspace, and then helps review, open PRs, and archive finished branches.
+
+## Generated files
+
+- \`.conductor/settings.toml\` configures shared Conductor repository scripts.
+- \`README.md\` documents how Conductor should use the existing Claude Code, Codex, and Cursor outputs from this repository.
+
+## Setup
+
+1. Install Conductor for macOS from https://www.conductor.build/.
+2. Open the repository you want Conductor to manage.
+3. Copy this output's \`.conductor/settings.toml\` into the repository root when the Build with WordPress package scripts are the workflow you want new Conductor workspaces to share.
+4. Install or sync the underlying agent configs for the agents you plan to run:
+   - Claude Code: use \`plugins/claude-code/\`.
+   - Codex: use \`plugins/codex/\`.
+   - Cursor: use \`plugins/cursor/\`.
+5. In Conductor, use Sync Agent Configs or the agent/provider settings to make the same MCP servers available to Claude Code, Codex, and Cursor.
+
+## Scripts
+
+Current Conductor docs recommend committed repository settings in \`.conductor/settings.toml\` for shared setup and run scripts. Legacy \`conductor.json\` is not generated because current docs mark it as legacy and Conductor ignores repo-level \`conductor.json\` once \`.conductor/settings.toml\` exists.
+
+The generated settings use:
+
+\`\`\`toml
+"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"
+
+[scripts]
+setup = "pnpm install"
+run = "pnpm build && pnpm verify"
+run_mode = "concurrent"
+\`\`\`
+
+Adjust \`scripts.setup\` and \`scripts.run\` for repositories that consume these WordPress.com agent files instead of developing this package directly. Use \`$CONDUCTOR_PORT\` in run scripts when a workspace starts a local web server.
+
+## MCP support
+
+Conductor supports MCP servers through the app's MCP/provider configuration and can sync agent configs between Claude Code and Codex. The current repository settings schema documents scripts, prompts, environment variables, providers, and Git behavior, but it does not define a repository-level MCP server table.
+
+For that reason this output does not invent a Conductor-specific MCP file. Use the existing MCP configs generated for the underlying agents:
+
+- Claude Code: \`plugins/claude-code/.mcp.json\`
+- Codex: \`plugins/codex/plugins/wordpress-studio/.mcp.json\`
+- Cursor: \`plugins/cursor/mcp.json\`
+
+Those configs launch the shared \`studio mcp\` server plus the bundled \`wordpress-telemetry\` server. Conductor's MCP support and Sync Agent Configs should point at the same shared substrate instead of adding another WordPress.com backend.
+
+## Message queues
+
+Conductor message queues are a native composer/workspace feature. They do not require generated files in this package. Queue multiple prompts in Conductor when a workspace needs ordered follow-up work; keep durable WordPress.com workflow guidance in the underlying agent outputs and shared skills.
+
+## Source links
+
+- Product overview: https://www.conductor.build/
+- Workflow and workspaces: https://www.conductor.build/docs/concepts/workflow and https://www.conductor.build/docs/concepts/workspaces-and-branches
+- Scripts and repository settings: https://www.conductor.build/docs/reference/scripts and https://www.conductor.build/docs/reference/settings
+- Settings reference: https://www.conductor.build/docs/reference/settings/reference
+- Legacy conductor.json: https://www.conductor.build/docs/reference/conductor-json
+- MCPs and message queues changelog: https://www.conductor.build/changelog/0.1.0-mcps-message-queues
+- Repo settings migration changelog: https://www.conductor.build/changelog/0.62.0-repo-settings-browser-preview
+- Sync agent configs changelog: https://www.conductor.build/changelog/0.57.0-sync-agent-configs
+`;
+}
+
 function buildOpenCodeReadme({ skillNames }) {
   const skillList = skillNames
     .map((skillName) => `- \`${skillName}\``)
@@ -2659,6 +2739,26 @@ async function buildContinueOutput() {
   console.log(`Built Continue output at ${continueOutputDir}`);
 }
 
+async function buildConductorOutput() {
+  await rm(conductorOutputDir, { recursive: true, force: true });
+  await mkdir(path.join(conductorOutputDir, ".conductor"), {
+    recursive: true,
+  });
+
+  await writeFile(
+    path.join(conductorOutputDir, ".conductor", "settings.toml"),
+    buildConductorSettings(),
+    "utf8",
+  );
+  await writeFile(
+    path.join(conductorOutputDir, "README.md"),
+    buildConductorReadme(),
+    "utf8",
+  );
+
+  console.log(`Built Conductor output at ${conductorOutputDir}`);
+}
+
 async function main() {
   await mkdir(pluginsDir, { recursive: true });
   await access(telemetryMcpServerDistPath);
@@ -2669,6 +2769,7 @@ async function main() {
   }
 
   await buildContinueOutput();
+  await buildConductorOutput();
 }
 
 main().catch((error) => {
diff --git a/scripts/verify-plugins.mjs b/scripts/verify-plugins.mjs
@@ -21,6 +21,7 @@ const codexMarketplacePath = path.join(
 const claudePluginDir = path.join(root, "plugins", "claude-code");
 const cursorPluginDir = path.join(root, "plugins", "cursor");
 const continueOutputDir = path.join(root, "plugins", "continue");
+const conductorOutputDir = path.join(root, "plugins", "conductor");
 const openCodePluginDir = path.join(root, "plugins", "opencode");
 const rooPluginDir = path.join(root, "plugins", "roo-code");
 const juniePluginDir = path.join(root, "plugins", "junie");
@@ -284,6 +285,50 @@ async function verifyContinueOutput() {
   }
 }
 
+async function verifyConductorOutput() {
+  await access(path.join(conductorOutputDir, "README.md"));
+  await access(path.join(conductorOutputDir, ".conductor", "settings.toml"));
+
+  const settings = await readFile(
+    path.join(conductorOutputDir, ".conductor", "settings.toml"),
+    "utf8",
+  );
+
+  if (!settings.includes('"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"')) {
+    throw new Error("Conductor settings are missing the repository schema URL");
+  }
+
+  if (!settings.includes("[scripts]")) {
+    throw new Error("Conductor settings must define a scripts table");
+  }
+
+  if (!settings.includes('setup = "pnpm install"')) {
+    throw new Error("Conductor settings are missing the setup script");
+  }
+
+  if (!settings.includes('run = "pnpm build && pnpm verify"')) {
+    throw new Error("Conductor settings are missing the run script");
+  }
+
+  const readme = await readFile(path.join(conductorOutputDir, "README.md"), "utf8");
+
+  if (!readme.includes("WordPress.com for Conductor")) {
+    throw new Error("Conductor README is missing the expected title");
+  }
+
+  if (!readme.includes("Legacy `conductor.json` is not generated")) {
+    throw new Error("Conductor README must explain why conductor.json is not generated");
+  }
+
+  if (!readme.includes("does not define a repository-level MCP server table")) {
+    throw new Error("Conductor README must explain MCP config boundaries");
+  }
+
+  if (!readme.includes("message queues are a native composer/workspace feature")) {
+    throw new Error("Conductor README must explain message queue boundaries");
+  }
+}
+
 async function verifyOpenCodePlugin(skillNames) {
   await access(path.join(openCodePluginDir, "README.md"));
   await access(path.join(openCodePluginDir, "AGENTS.md"));
@@ -841,6 +886,7 @@ async function main() {
   await verifyClaudePlugin(skillNames);
   await verifyCursorPlugin(skillNames);
   await verifyContinueOutput();
+  await verifyConductorOutput();
   await verifyOpenCodePlugin(skillNames);
   await verifyKiloCodePlugin(skillNames);
   await verifyRooPlugin(skillNames);
@@ -857,7 +903,7 @@ async function main() {
   await verifyAmpPlugin(skillNames);
   await verifyPiPlugin(skillNames);
 
-  console.log("Codex, Claude, Cursor, Continue, OpenCode, Kilo Code, Roo Code, Cline, Junie, Gemini, Copilot, Qodo, Zed, Windsurf, Aider, Factory Droid, Devin, Amp, and Pi verification passed");
+  console.log("Amp, Cline, Codex, Claude, Conductor, Cursor, Continue, OpenCode, Kilo Code, Roo Code, Junie, Gemini, Copilot, Qodo, Zed, Windsurf, Aider, Factory Droid, Devin, and Pi verification passed");
 }
 
 main().catch((error) => {
