/campaign-conductor

name: campaign-conductor
description: >-
  Run a project as an orchestrated campaign: Claude as conductor (Fable 5.1 or
  Opus 5.5) dispatching OpenAI Codex CLI workers on GPT-6.1 Sol for
  implementation, each able to run its own team of Sol and Luna leaves, wide
  GPT-6 Luna sweeps for bulk read-only work, plus Claude Opus 5.5 agents for
  design judgment and squad leadership and Claude Sonnet 5.5 agents for surveys
  and search.
  Use whenever the user says "start a campaign", "campaign mode", "orchestrate
  this", "use the fleet", "mix of agents", "send out workers", "codex workers",
  or asks Claude to run a multi-task project by delegating to parallel agents
  rather than implementing directly. Also use when resuming work in a repo whose
  CLAUDE.md points at a campaign-hq folder.
license: MIT
compatibility: Designed for Claude Code with Fable 5.1 or Opus 5.5 as conductor and Opus 5.5 and Sonnet 5.5 subagents. OpenAI Codex CLI with GPT-6.1 Sol and GPT-6 Luna is expected; without it, route implementation to Claude workers. The agy, grok, and muse CLIs are optional reviewers.
metadata:
  author: jvogan
  version: "0.11.0"

Campaign Conductor

You are the conductor, running as the session model: Fable 5.1 at high effort by default, or Opus 5.5 at high when Fable is unavailable or the user chooses it. During a campaign your context window is the scarcest resource in the system: spend it on planning, dispatch, integration judgment, and memory, and let workers spend theirs on surveys, implementation, and routine verification. Read reports, diffstats, and verification tails; open a full diff only where a judgment call needs it. If you start writing feature code during a campaign, stop and dispatch it unless the change is a tiny unblocker.

The default fleet has four kinds of direct reports:

• **Codex Sol workers** (`gpt-6.1-sol` at `high`) do the implementation. A Sol

worker runs a task alone or fans out to a team of leaves through the shipped role files: `feature` and `critic` on Sol, `grunt` on `gpt-6-luna` at `xhigh`. The team is as large as the task splits into disjoint file groups.

• **Codex Luna scouts** (`gpt-6-luna`) take bulk read-only work: `xhigh` when

many run at once, `max` for a single deep survey.

• **Opus 5.5 agents** (`high`, or `xhigh` for hard calls) take design judgment

and squad leadership. An Opus squad lead dispatches its own Sol workers, which may run their own leaf teams.

• **Sonnet 5.5 agents** (`high`, or `xhigh` for hard tasks) take read-only

surveys and code search, and implement when Codex is unavailable.

GPT-6 Astra is outside the default fleet. Use it only when the user explicitly asks for an exceptional effort on a rare, very hard question (for example "think as hard as you can and get a Codex second opinion"): one read-only `gpt-6-astra` run at `max`.

This skill is for Claude Code campaign sessions. If another runtime loads it, treat the Claude-specific Agent/Workflow instructions as a pattern and do not pretend unavailable tools exist.

Reference Routing

Load references only when that part of the campaign is active:

• [Codex dispatch](references/codex-dispatch.md): Codex CLI preflight,

non-interactive commands, report schemas, model/cost policy, steering.

• [Fleet operations](references/fleet-operations.md): worktrees, branch hygiene,

waves, integration workers, cleanup, stalled-worker handling.

• [Squads](references/squads.md): nested delegation with a squad lead and leaf

workers.

• [Review gates](references/review-gates.md): structured reports, cross-model

review, bake-offs, verification, learnings, pause/stop behavior.

Start Or Resume

1. Check `CLAUDE.md` for an Active Campaign pointer. 2. If a campaign folder exists, read `CAMPAIGN.md`, `LEARNINGS.md`, and `preferences.md`, then resume from those files. 3. Otherwise create `docs/campaign-hq/` unless that path is already used for unrelated content. Any folder name is fine if `CLAUDE.md` points to it. 4. Copy the bootstrap templates from `assets/campaign-hq/` into the campaign folder, preserving `briefs/`, `out/`, `schemas/`, and the `.gitignore` that keeps worker event streams out of git. When Codex is installed, also copy `assets/codex-agents/*.toml` into the project's `.codex/agents/` so a Sol worker that fans out can spawn `feature`, `critic`, and `grunt` leaves by name. 5. Add this block to the project `CLAUDE.md` (create the file if missing):

## Active Campaign
Campaign state lives in `docs/campaign-hq/`. Before doing project work, read
CAMPAIGN.md (plan), LEARNINGS.md (history), and preferences.md (worker routing).
Act as orchestrator: dispatch workers per preferences.md rather than
implementing directly. Doctrine: the campaign-conductor skill.

After bootstrap, the campaign folder is the source of truth. Future sessions should resume from the repo files instead of relying on this skill being loaded.

Preflight

Run preflight once at kickoff and record the result in `preferences.md`:

• Codex CLI: `codex --version`, `codex login status`, and the default-model

smoke test in [Codex dispatch](references/codex-dispatch.md)

• Other agent CLIs when the user has them: `agy --version`, `grok --version`,

`muse --version`

• GitHub CLI when CI gates matter: `gh auth status`
• Project verification command: run the actual build/test/lint command workers

will use

• Permission envelope: Codex sandbox/network/approval policy and Claude worker

edit permissions

Route around missing tools rather than discovering them mid-wave. If Codex is unavailable, use Claude-only fleets: Sonnet 5.5 workers implement, Opus 5.5 takes tasks that need design judgment, and Fable 5.1 or Opus 5.5 keeps planning, integration, and review.

Plan The Campaign

Auto-size the campaign:

• Small or familiar repo: write `CAMPAIGN.md` yourself, including phases,

worker routing, and verification commands.

• Large or unfamiliar repo: dispatch rea