orchestrator-supaconductor

What's New in v3.7.0

• Board of Directors fast-path — Routine tracks now use a single Opus call (all 5 lenses in one pass) at ~1/10th the cost of the full multi-agent deliberation. Full board is reserved for high-stakes decisions: production deploys, security architecture, breaking API changes, data-loss migrations.
• Plan revision guard — Prevents infinite planning loops. Tracks the number of times a plan is rejected and calls it done (with warnings) after 3 revisions.
• Execution state reconciliation — On session resume, plan.md checkboxes are now treated as the source of truth. Prevents already-completed tasks from being re-executed after a crash.
• Atomic file locks — Parallel workers can no longer accidentally acquire the same file lock simultaneously. Uses fcntl OS-level locking on a dedicated mutex file.
• Bounded knowledge injection — The knowledge brief injected before planning is capped at 500 tokens (top-3 most relevant patterns and errors). Prevents context growth as your project's knowledge base accumulates.

What Does This Do?

You tell Claude Code what you want. SupaConductor figures out how to build it — step by step, with quality checks at every stage.

Without SupaConductor, you prompt Claude Code and hope for the best. You manually review, re-prompt, and fix what it misses.

With SupaConductor, you type one command:

/orchestrator-supaconductor:go Add user authentication with Google OAuth

And it automatically:

1. Writes a detailed specification
2. Creates an implementation plan with task dependencies
3. Executes each task (in parallel when possible)
4. Checks the work with specialized evaluators
5. Fixes any issues it finds
6. Marks the work complete when everything passes

No babysitting. No re-prompting. Just describe what you want and walk away.

What's Inside

Bundles Superpowers v4.3.0 (MIT) — everything works out of the box with zero setup.

Installation

Option 1: Marketplace (recommended)

Open Claude Code and run:

/install Ibrahim-3d/orchestrator-supaconductor

Option 2: Clone from GitHub

git clone https://github.com/Ibrahim-3d/orchestrator-supaconductor.git ~/.claude/plugins/orchestrator-supaconductor

Option 3: Download manually

Download the latest release and extract it to ~/.claude/plugins/orchestrator-supaconductor/.

Verify it works

Start a new Claude Code session and type /orchestrator-supaconductor:. You should see a list of commands appear. If you see /orchestrator-supaconductor:go, you're all set.

Getting Started

Step 1: Set up your project

Open Claude Code in your project folder and run:

/orchestrator-supaconductor:setup

This walks you through an interactive setup that:

• Analyzes your existing codebase (or starts fresh for new projects)
• Helps define your product vision and tech stack
• Creates a conductor/ folder in your project to track all work
• Generates an initial development sprint with ready-to-execute tracks

You only need to do this once per project.

Step 2: Build something

Tell it what you want in plain English:

/orchestrator-supaconductor:go Add Stripe payment integration with webhooks

/orchestrator-supaconductor:go Fix the login bug where users get logged out after refresh

/orchestrator-supaconductor:go Build a dashboard with real-time analytics charts

/orchestrator-supaconductor:go Refactor the database layer to use connection pooling

That's it. SupaConductor takes over from here — planning, coding, testing, and evaluating the work automatically.

Step 3: Check on progress

/orchestrator-supaconductor:status

Shows all your active tracks, what step each one is on, and what's completed.

Step 4: Resume interrupted work

If a session ends before a track completes, just run:

/orchestrator-supaconductor:go

It picks up exactly where it left off.

How It Works

Every piece of work follows a structured cycle called the Evaluate-Loop:

The loop runs fully automated. It stops when the work passes all quality checks or when it needs your input.

Parallel Execution

When tasks don't depend on each other, they run simultaneously:

This means a feature with 6 tasks might only take as long as 3, because independent tasks run in parallel.

Two Modes

SupaConductor can work in two ways:

Switch modes by editing conductor/config.json in your project:

{ "mode": "agentic" }

{ "mode": "human-in-the-loop" }

Board of Directors

For major decisions — and automatically for high-stakes tracks like production deploys, security architecture changes, breaking API migrations, or data-loss operations — a virtual board deliberates with written rationale:

Each director independently assesses your question, then they discuss and vote with written rationale.

/orchestrator-supaconductor:board-meeting Should we migrate from REST to GraphQL?

/orchestrator-supaconductor:board-review Add real-time notifications via WebSocket

Use board-meeting for full deliberation (detailed, takes longer) or board-review for quick assessments.

All Commands

The Main Ones

Quality and Review