orchestrator-supaconductor

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

What's Inside

| Component | Count | What It Does | |-----------|------:|-------------| | Commands | 36 | Slash commands you type to control everything | | Skills | 39 | Specialized knowledge modules that activate when needed | | Agents | 15 | Autonomous workers that handle planning, coding, and evaluation | | Evaluators | 4 | Quality checkers for UI/UX, code quality, integrations, and business logic | | Board of Directors | 5 | Virtual executives who deliberate on major decisions | | Lead Engineers | 4 | Architecture, Product, Tech, and QA specialists |

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:

| Step | What Happens | |------|-------------| | Plan | Breaks your goal into tasks with a dependency graph | | Evaluate Plan | Checks for scope issues, overlap with other work, and feasibility | | Execute | Writes code, runs tests, tracks progress — parallel when possible | | Evaluate Execution | Specialized checkers review UI/UX, code quality, integrations, and business logic | | Fix | Addresses any failures, then loops back to evaluation (up to 5 fix cycles; up to 3 plan revisions) | | Complete | All checks pass — track is marked done |

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:

| Mode | Behavior | Best For | |------|----------|----------| | Agentic (default) | Fully autonomous — makes all decisions itself | Experienced users who trust the system | | Human-in-the-loop | Pauses at key decision points to ask you | Learning the system, critical work, or when you want more control |

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:

| Director | Focus | |----------|-------| | Chief Architect | System design, scalability, technical debt | | Chief Product Officer | User value, market fit, feature scope | | Chief Security Officer | Vulnerabilities, compliance, data protection | | Chief Operations Officer | Feasibility, timelines, deployment risks | | Chief Experience Officer | UX/UI, accessibility, user journeys |

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

| Command | What It Does | |---------|-------------| | /orchestrator-supaconductor:go <goal> | Describe what you want — everything else is automatic | | /orchestrator-supaconductor:setup | Set up SupaConductor in your project (run once) | | /orchestrator-supaconductor:status | See all your tracks and their progress | | /orchestrator-supaconductor:implement | Continue the Evaluate-Loop on the current track | | /orchestrator-supaconductor:new-track | Create a new track with more manual control |

Quality and Review

| Command | What It Does | |---------|-------------| | /orchestrator-supaconductor:phase-review | Run a quality gate on completed work | | /orchestrator-supaconductor:cto-advisor | Get a CTO-level architecture review | | /orchestrator-supaconductor:board-meeting <topic> | Full board deliberation with voting | | `/orchestrator-supaconductor:board-review <