conductor
Multi-agent orchestration protocol for coordinating parallel Claude instances. Prevents file conflicts, enforces priority alignment, and provides real-time visibility across all running agents. Use /conductor to start tasks, claim files, check status, and release claims.
What this skill does
# Conductor: Multi-Agent Orchestration Protocol Conductor coordinates multiple Claude Code instances working in parallel. It prevents conflicts, enforces strategic alignment, and provides visibility into what each agent is doing. ## Quick Reference ```bash /conductor start "task description" --project name --priority P1|P2|P3 /conductor status # Show all active instances /conductor claim path/to/file.ts # Lock files before editing /conductor release # Release your file claims /conductor done # Mark task complete, release all claims /conductor align # Check task against north-stars /conductor conflicts # Show any active conflicts ``` ## Core Concepts ### The Problem When running 3-5+ Claude instances simultaneously: - **Conflicting changes**: Two agents edit the same file - **Strategic drift**: Agents work on low-priority tasks - **Lost visibility**: No idea what each instance is doing - **Wasted effort**: Duplicate work or incompatible changes ### The Solution A lightweight coordination protocol where: 1. Each agent **registers** when starting a task 2. Agents **claim files** before editing them 3. A **priority gate** rejects misaligned work 4. A **status dashboard** shows all activity ## How It Works ### Status File Location Global coordination state lives at: ``` ~/.conductor/ ├── status.json # Current state of all instances ├── history.jsonl # Completed tasks log └── conflicts.log # Conflict history for learning ``` ### Instance Lifecycle ``` ┌─────────────────────────────────────────────────────────────┐ │ INSTANCE LIFECYCLE │ ├─────────────────────────────────────────────────────────────┤ │ │ │ /conductor start "Fix auth bug" --project pitchello │ │ │ │ │ ▼ │ │ ┌─────────────────┐ │ │ │ Priority Check │──Fail──▶ ⚠️ Drift warning │ │ │ (vs north-stars)│ (require override) │ │ └────────┬────────┘ │ │ │ Pass │ │ ▼ │ │ ┌─────────────────┐ │ │ │ Register in │ │ │ │ status.json │ │ │ └────────┬────────┘ │ │ │ │ │ ▼ │ │ /conductor claim src/auth.ts src/lib/session.ts │ │ │ │ │ ▼ │ │ ┌─────────────────┐ │ │ │ Conflict Check │──Conflict──▶ ⚠️ File locked │ │ └────────┬────────┘ (coordinate) │ │ │ Clear │ │ ▼ │ │ ✅ Work on task (files are claimed) │ │ │ │ │ ▼ │ │ /conductor done │ │ │ │ │ ▼ │ │ ┌─────────────────┐ │ │ │ Release claims │ │ │ │ Log to history │ │ │ │ Remove from │ │ │ │ status.json │ │ │ └─────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────┘ ``` ## Commands Detail ### /conductor start Register a new task with the conductor. ```bash /conductor start "Implement user authentication" --project pitchello --priority P1 ``` **What it does:** 1. Generates unique instance ID (e.g., `itm-a1b2c3`) 2. Checks priority against north-stars alignment 3. Registers in `~/.conductor/status.json` 4. Returns instance ID for reference **Flags:** - `--project` (required): Project name (pitchello, mission-control, digital-self, etc.) - `--priority` (required): P1 (critical), P2 (important), P3 (nice-to-have) - `--override` (optional): Skip priority gate with justification ### /conductor claim Lock files before editing to prevent conflicts. ```bash /conductor claim src/api/users.ts src/lib/auth.ts ``` **What it does:** 1. Checks if any file is already claimed 2. If clear, adds files to your instance's `files_claimed` array 3. If conflict, shows who has the file and suggests coordination **Best practice:** Claim files at the start of work, not mid-task. ### /conductor status Show dashboard of all active instances. ```bash /conductor status ``` **Output:** ``` ┌─────────────────────────────────────────────────────────────┐ │ CONDUCTOR STATUS - 2026-01-17 10:30 │ ├─────────────────────────────────────────────────────────────┤ │ ACTIVE INSTANCES (3) │ ├─────────────────────────────────────────────────────────────┤ │ [itm-a1b2] pitchello │ P1 │ Fix auth bug │ 45m │ │ └─ src/api/users.ts, src/lib/auth.ts │ │ │ │ [itm-c3d4] mission-control │ P1 │ Lead scoring API │ 30m │ │ └─ app/api/agent/leads/* │ │ │ │ [cur-e5f6] digital-self │ P2 │ Content draft │ 15m │ │ └─ (no files claimed) │ ├─────────────────────────────────────────────────────────────┤ │ CONFLICTS: None │ │ DRIFT WARNINGS: 1 (cur-e5f6 working on P2 during P1 sprint) │ └─────────────────────────────────────────────────────────────┘ ``` ### /conductor done Complete your task and release all claims. ```bash /conductor done ``` **What it does:** 1. Releases all file claims 2. Logs task to `~/.conductor/history.jsonl` 3. Removes instance from `status.json` ### /conductor align Check if your current/proposed task aligns with strategic priorities. ```bash /conductor align "Add dark mode to settings" ``` **What it does:** 1. Reads `north-stars.md` from digital-self 2. Reads current sprint priorities (if defined) 3. Returns alignment assessment ### /conductor release Release file claims without completing the task (e.g., when switching focus). ```bash /conductor release src/api/users.ts # or release all /conductor release --all ``` ### /conductor conflicts Show detailed conflict information. ```bash /conductor conflicts ``` ## Integration Points ### With /daily-brief At session start, daily-brief should: 1. Run `/conductor status` to show active instances 2. Flag any orphaned instances (started >24h ago) 3. Suggest cleanup if needed ### With /shutdown At session end, shutdown should: 1. Run `/conductor done` to release this instance's claims 2. Log final status to history ### With File Edits When editing files, agents should: 1. Check if file is claimed before editing 2. If not claimed, claim it first 3. If claimed by another, coordinate or wait ## Priority Levels | Level | Description | Examples | |-------|-------------|----------| | P1 | Critical, sprint-blocking | Revenue features, production bugs | | P2 | Important, planned work | Backlog items, improvements
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.