by Ibrahim-3d
Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills
# Add to your Claude Code skills
git clone https://github.com/Ibrahim-3d/conductor-orchestrator-superpowersGuides for using ai agents skills like conductor-orchestrator-superpowers.
Last scanned: 5/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-30T15:06:06.828Z",
"npmAuditRan": true,
"pipAuditRan": true
}conductor-orchestrator-superpowers is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Ibrahim-3d. Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. It has 296 GitHub stars.
Yes. conductor-orchestrator-superpowers passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers" and add it to your Claude Code skills directory (see the Installation section above).
conductor-orchestrator-superpowers is primarily written in Python. It is open-source under Ibrahim-3d on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh conductor-orchestrator-superpowers against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ CRITICAL: PLUGIN RENAMED TO SUPACONDUCTOR This plugin has been renamed from
conductor-orchestrator-superpowerstosupaconductor. Existing users MUST follow the Migration Guide below to avoid command failures.
If you have the old conductor-orchestrator-superpowers plugin installed, you must perform these steps to migrate to SupaConductor:
/plugin in Claude Code, find conductor-orchestrator-superpowers, and disable/remove it.~/.claude/plugins/conductor-orchestrator-superpowers (or wherever you cloned it)./supaconductor:setup in those projects to update the internal references.Why the change? We renamed from conductor-orchestrator-superpowers to supaconductor because the old name was too long and causing path-length issues in some environments. All your existing tracks and data are safe, but the commands you use to interact with them have changed to the /supaconductor: namespace.
Conductor turns Claude Code into a structured engineering team. Instead of ad-hoc coding, it organizes work into tracks with specs, plans, parallel execution, and automated evaluation.
One command. Full automation.
/supaconductor:go Add user authentication with OAuth
That single command triggers the full lifecycle — spec, plan, execute, evaluate, fix — without any manual handoffs.
| Component | Count | Highlights |
|---|---|---|
| Agents | 16 | Orchestrator, loop agents, board directors, executive advisors, workers |
| Skills | 42 | Planning, execution, evaluation, debugging, TDD, code review |
| Commands | 22 | /supaconductor:go, /supaconductor:setup, /supaconductor:board-meeting, /supaconductor:cto-advisor, and more |
| Evaluators | 4 | UI/UX, Code Quality, Integration, Business Logic |
| Board of Directors | 5 | Chief Architect, CPO, CSO, COO, CXO |
| Lead Engineers | 4 | Architecture, Product, Tech, QA |
Bundles superpowers v4.3.0 (MIT) — no external dependencies.
/plugin marketplace add Ibrahim-3d/conductor-orchestrator-supaconductor
/plugin install conductor-orchestrator-supaconductor@ibrahim-plugins
git clone https://github.com/Ibrahim-3d/conductor-orchestrator-supaconductor.git ~/.claude/plugins/conductor-orchestrator-supaconductor
Download the latest release and extract to ~/.claude/plugins/conductor-orchestrator-supaconductor/.
Start a new Claude Code session. Type / and check for /supaconductor:go, /supaconductor:implement, /supaconductor:board-meeting in the command list.
1. Initialize Conductor in your project:
/supaconductor:setup
Creates a conductor/ directory with track registry, workflow docs, and knowledge base.
2. Build something:
/supaconductor:go Add Stripe payment integration with webhooks
/supaconductor:go Fix the login bug where users get logged out after refresh
/supaconductor:go Build a dashboard with real-time analytics charts
/supaconductor:go Refactor the database layer to use connection pooling
3. Monitor and control:
/supaconductor:status # See all tracks and progress
/supaconductor:implement # Continue work on current track
/supaconductor:new-track # Create a track manually
/supaconductor:phase-review # Run quality gate evaluation
Every track follows a rigorous, automated cycle:
| Step | What Happens |
|---|---|
| Plan | Generates implementation steps with dependency graph (DAG) |
| Evaluate Plan | Checks scope, overlap with existing tracks, feasibility |
| Execute | Implements code, runs tests, updates progress |
| Evaluate Execution | Dispatches specialized evaluators (UI/UX, code quality, integration, business logic) |
| Fix | Addresses failures, loops back to evaluation (max 3 cycles) |
| Complete | All evaluators pass — track marked done |
| Retrospective | Extracts reusable patterns and error fixes to knowledge layer |
The loop runs fully automated. It stops when the track is complete, when the fix cycle exceeds 3 iterations, or when it needs human input.
Tasks without dependencies run simultaneously via DAG scheduling:
The orchestrator reads the dependency graph and dispatches independent tasks to parallel worker agents. When all upstream dependencies resolve, downstream tasks start automatically.
For major architectural and strategic decisions, a 5-member board deliberates across 5 phases:
| Director | Domain | Focus |
|---|---|---|
| Chief Architect | Technical | System design, patterns, scalability, tech debt |
| Chief Product Officer | Product | User value, market fit, scope discipline |
| Chief Security Officer | Security | Vulnerabilities, compliance, data protection |
| Chief Operations Officer | Operations | Feasibility, timeline, resources, deployment |
| Chief Experience Officer | Experience | UX/UI, accessibility, user journey |
Each director independently assesses, then they discuss and vote with written rationale.
/supaconductor:board-meeting Should we migrate from REST to GraphQL?
/supaconductor:board-review Add real-time notifications via WebSocket
| Command | Description |
|---|---|
/supaconductor:go <goal> |
State your goal — Conductor handles everything |
/supaconductor:status |
View all tracks and current progress |
/supaconductor:implement |
Run the Evaluate-Loop on current track |
/supaconductor:new-track |
Create a new track with spec and plan |
/supaconductor:setup |
Initialize Conductor in a project |
| Command | Description |
|---|---|
/supaconductor:phase-review |
Post-execution quality gate |
/supaconductor:cto-advisor |
CTO-level architecture review |
/supaconductor:board-meeting <topic> |
Full board deliberation (4 phases) |
/supaconductor:board-review <topic> |
Quick board assessment |
/supaconductor:ui-audit |
UI/UX accessibility audit |
| Command | Description |
|---|---|
/supaconductor:ceo |
Strategic business advice |
/supaconductor:cmo |
Marketing strategy guidance |
/supaconductor:cto |
Technical architecture guidance |
/supaconductor:ux-designer |
UX strategy and design guidance |
| Command | Description |
|---|---|
/supaconductor:writing-plans |
Create a plan using superpowers patterns |
/supaconductor:executing-plans |
Execute a plan using superpowers patterns |
/supaconductor:brainstorm |
Creative problem-solving session |
┌─────────────────────────────────────────────────────────────┐
│ /go <your goal> │
│ │ │
│ ┌──────────▼──────────┐ │
│ │ Orchestrator │ conductor-orchestrator │
│ │ (master loop) │ │
│ └──────────┬──────────┘ │
│ │ │
│ ┌────────────────────┼────────────────────┐ │
│ ▼