Skip to content
Back to search

ibrahim-plugins

MarketplaceWorks with Claude CodeGitHub

Official Claude Code plugins by Ibrahim — AI image generation, multi-agent orchestration, and more

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ibrahim-3d-orchestrator-supaconductor/badge.svg)](/listings/ibrahim-3d-orchestrator-supaconductor)

HTML

<a href="/listings/ibrahim-3d-orchestrator-supaconductor"><img src="/api/listings/ibrahim-3d-orchestrator-supaconductor/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

SupaConductor now targets multiple coding-agent hosts from one canonical source. See [Platform Support](docs/platform-support.md) for exact capability differences and package layouts.

Claude Code — native plugin

/plugin marketplace add Ibrahim-3d/orchestrator-supaconductor
/plugin install orchestrator-supaconductor@ibrahim-plugins

Update later:

claude plugin marketplace update ibrahim-plugins
claude plugin update orchestrator-supaconductor@ibrahim-plugins

Codex, Cursor, Antigravity, Windsurf, and GitHub Copilot

git clone https://github.com/Ibrahim-3d/orchestrator-supaconductor.git
cd orchestrator-supaconductor
python3 scripts/build-platform-adapters.py

Packages are generated under `dist/platforms/`; published releases also attach ready-to-use ZIP packages.

| Host | Package | |---|---| | OpenAI Codex / ChatGPT desktop | `dist/platforms/codex/orchestrator-supaconductor` | | Cursor | `dist/platforms/cursor/orchestrator-supaconductor` | | Google Antigravity | `dist/platforms/antigravity/orchestrator-supaconductor` | | Windsurf / Cascade | `dist/platforms/windsurf/orchestrator-supaconductor` | | GitHub Copilot | `dist/platforms/copilot/orchestrator-supaconductor` |

See [docs/platform-support.md](docs/platform-support.md) for installation paths and command/agent mapping.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 70 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "ibrahim-plugins",
  3. "description": "Official Claude Code plugins by Ibrahim — AI image generation, multi-agent orchestration, and more",
  4. "version": "3.8.0",
  5. "owner": {
  6. "name": "Ibrahim",
  7. "url": "https://github.com/Ibrahim-3d"
  8. },
  9. "plugins": [
  10. {
  11. "name": "orchestrator-supaconductor",
  12. "source": {
  13. "source": "github",
  14. "repo": "Ibrahim-3d/orchestrator-supaconductor"
  15. },
  16. "description": "Conductor v3 — Multi-agent orchestration with Evaluate-Loop, parallel execution, Board of Directors, and bundled SupaConductor skills for Claude Code",
  17. "version": "3.8.0",
  18. "author": {
  19. "name": "Ibrahim",
  20. "url": "https://github.com/Ibrahim-3d"
  21. },
  22. "homepage": "https://github.com/Ibrahim-3d/orchestrator-supaconductor",
  23. "repository": "https://github.com/Ibrahim-3d/orchestrator-supaconductor",
  24. "license": "AGPL-3.0",
  25. "keywords": [
  26. "orchestration",
  27. "evaluate-loop",
  28. "conductor",
  29. "orchestrator-supaconductor",
  30. "parallel-agents",
  31. "board-of-directors",
  32. "tdd",
  33. "debugging",
  34. "planning",
  35. "multi-agent"
  36. ],
  37. "category": "productivity"
  38. },
  39. {
  40. "name": "nano-banana",
  41. "source": {
  42. "source": "github",
  43. "repo": "Ibrahim-3d/nano-banana-claude-plugin"
  44. },
  45. "description": "AI image generation & editing for Claude Code powered by Google Gemini 3.1 API. Text-to-image, inpainting, style transfer, 4K upscaling, search grounding, and multi-reference composition.",
  46. "version": "2.1.0",
  47. "author": {
  48. "name": "Ibrahim",
  49. "url": "https://github.com/Ibrahim-3d"
  50. },
  51. "homepage": "https://github.com/Ibrahim-3d/nano-banana-claude-plugin",
  52. "repository": "https://github.com/Ibrahim-3d/nano-banana-claude-plugin",
  53. "license": "MIT",
  54. "keywords": [
  55. "image-generation",
  56. "gemini",
  57. "gemini-3.1",
  58. "ai-art",
  59. "text-to-image",
  60. "image-editing",
  61. "style-transfer",
  62. "4k-generation",
  63. "multi-reference",
  64. "nano-banana",
  65. "claude-code-plugin"
  66. ],
  67. "category": "creative"
  68. }
  69. ]
  70. }
README.md · README · 502 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <p align="center">
  2. <img src="assets/conductor-banner.png" alt="SupaConductor" width="800"/>
  3. </p>
  4. <h1 align="center">SupaConductor</h1>
  5. <p align="center">
  6. <strong>Turn your coding agent into a full engineering team.</strong><br/>
  7. One command builds features, fixes bugs, and ships code — with automated planning, execution, and quality checks.
  8. </p>
  9. <p align="center">
  10. <a href="LICENSE"><img alt="AGPL-3.0 License" src="https://img.shields.io/badge/license-AGPL--3.0-blue.svg"/></a>
  11. <a href="https://github.com/Ibrahim-3d/orchestrator-supaconductor/releases/latest"><img alt="Latest Release" src="https://img.shields.io/github/v/release/Ibrahim-3d/orchestrator-supaconductor?display_name=tag"/></a>
  12. <a href="https://docs.anthropic.com/en/docs/claude-code"><img alt="Claude Code" src="https://img.shields.io/badge/Claude_Code-native-blueviolet.svg"/></a>\n <a href="docs/platform-support.md"><img alt="Codex" src="https://img.shields.io/badge/Codex-Agent_Plugin-black.svg"/></a>\n <a href="docs/platform-support.md"><img alt="Cursor" src="https://img.shields.io/badge/Cursor-native-111111.svg"/></a>\n <a href="docs/platform-support.md"><img alt="Antigravity" src="https://img.shields.io/badge/Antigravity-native-4285F4.svg"/></a>\n <a href="docs/platform-support.md"><img alt="Windsurf" src="https://img.shields.io/badge/Windsurf-adapter-00BFA5.svg"/></a>
  13. <a href="https://github.com/Ibrahim-3d/orchestrator-supaconductor/discussions"><img alt="Community" src="https://img.shields.io/badge/community-discussions-orange.svg"/></a>
  14. </p>
  15. <p align="center">
  16. <a href="#what-does-this-do">What Is This?</a> &bull;
  17. <a href="#installation">Install</a> &bull;\n <a href="docs/platform-support.md">Platforms</a> &bull;
  18. <a href="#getting-started">Get Started</a> &bull;
  19. <a href="#how-it-works">How It Works</a> &bull;
  20. <a href="#all-commands">Commands</a> &bull;
  21. <a href="#faq">FAQ</a> &bull;
  22. <a href="ROADMAP.md">Roadmap</a> &bull;
  23. <a href="#community">Community</a>
  24. </p>
  25. ---
  26. ## Latest Release
  27. See the [latest GitHub Release](https://github.com/Ibrahim-3d/orchestrator-supaconductor/releases/latest) for current changes, fixes, upgrade notes, and known limitations. The [changelog](CHANGELOG.md) keeps the full version history.
  28. ---
  29. ## What Does This Do?
  30. You tell your coding agent what you want. SupaConductor figures out how to build it — step by step, with quality checks at every stage.
  31. **Without SupaConductor**, you prompt your coding agent and hope for the best. You manually review, re-prompt, and fix what it misses.
  32. **With SupaConductor**, you type one command:
  33. ```
  34. /orchestrator-supaconductor:go Add user authentication with Google OAuth
  35. ```
  36. And it automatically:
  37. 1. Writes a detailed specification
  38. 2. Creates an implementation plan with task dependencies
  39. 3. Executes each task (in parallel when possible)
  40. 4. Checks the work with specialized evaluators
  41. 5. Fixes any issues it finds
  42. 6. Marks the work complete when everything passes
  43. No babysitting. No re-prompting. Just describe what you want and walk away.
  44. ---
  45. ## What's Inside
  46. | Component | Count | What It Does |
  47. |-----------|------:|-------------|
  48. | **Commands** | 36 | Slash commands you type to control everything |
  49. | **Skills** | 39 | Specialized knowledge modules that activate when needed |
  50. | **Agents** | 15 | Autonomous workers that handle planning, coding, and evaluation |
  51. | **Evaluators** | 4 | Quality checkers for UI/UX, code quality, integrations, and business logic |
  52. | **Board of Directors** | 5 | Virtual executives who deliberate on major decisions |
  53. | **Lead Engineers** | 4 | Architecture, Product, Tech, and QA specialists |
  54. Bundles [Superpowers](https://github.com/obra/superpowers) v4.3.0 (MIT) — everything works out of the box with zero setup.
  55. ---
  56. ## Installation
  57. SupaConductor now targets multiple coding-agent hosts from one canonical source. See [Platform Support](docs/platform-support.md) for exact capability differences and package layouts.
  58. ### Claude Code — native plugin
  59. ```
  60. /plugin marketplace add Ibrahim-3d/orchestrator-supaconductor
  61. /plugin install orchestrator-supaconductor@ibrahim-plugins
  62. ```
  63. Update later:
  64. ```bash
  65. claude plugin marketplace update ibrahim-plugins
  66. claude plugin update orchestrator-supaconductor@ibrahim-plugins
  67. ```
  68. ### Codex, Cursor, Antigravity, Windsurf, and GitHub Copilot
  69. ```bash
  70. git clone https://github.com/Ibrahim-3d/orchestrator-supaconductor.git
  71. cd orchestrator-supaconductor
  72. python3 scripts/build-platform-adapters.py
  73. ```
  74. Packages are generated under `dist/platforms/`; published releases also attach ready-to-use ZIP packages.
  75. | Host | Package |
  76. |---|---|
  77. | OpenAI Codex / ChatGPT desktop | `dist/platforms/codex/orchestrator-supaconductor` |
  78. | Cursor | `dist/platforms/cursor/orchestrator-supaconductor` |
  79. | Google Antigravity | `dist/platforms/antigravity/orchestrator-supaconductor` |
  80. | Windsurf / Cascade | `dist/platforms/windsurf/orchestrator-supaconductor` |
  81. | GitHub Copilot | `dist/platforms/copilot/orchestrator-supaconductor` |
  82. See [docs/platform-support.md](docs/platform-support.md) for installation paths and command/agent mapping.
  83. ---
  84. ## Getting Started
  85. ### Step 1: Set up your project
  86. Open Claude Code in your project folder and run:
  87. ```
  88. /orchestrator-supaconductor:setup
  89. ```
  90. This walks you through an interactive setup that:
  91. - Analyzes your existing codebase (or starts fresh for new projects)
  92. - Helps define your product vision and tech stack
  93. - Creates a `conductor/` folder in your project to track all work
  94. - Generates an initial development sprint with ready-to-execute tracks
  95. You only need to do this once per project.
  96. ### Step 2: Build something
  97. Tell it what you want in plain English:
  98. ```
  99. /orchestrator-supaconductor:go Add Stripe payment integration with webhooks
  100. ```
  101. ```
  102. /orchestrator-supaconductor:go Fix the login bug where users get logged out after refresh
  103. ```
  104. ```
  105. /orchestrator-supaconductor:go Build a dashboard with real-time analytics charts
  106. ```
  107. ```
  108. /orchestrator-supaconductor:go Refactor the database layer to use connection pooling
  109. ```
  110. That's it. SupaConductor takes over from here — planning, coding, testing, and evaluating the work automatically.
  111. ### Step 3: Check on progress
  112. ```
  113. /orchestrator-supaconductor:status
  114. ```
  115. Shows all your active tracks, what step each one is on, and what's completed.
  116. ### Step 4: Resume interrupted work
  117. If a session ends before a track completes, just run:
  118. ```
  119. /orchestrator-supaconductor:go
  120. ```
  121. It picks up exactly where it left off.
  122. ---
  123. ## How It Works
  124. Every piece of work follows a structured cycle called the **Evaluate-Loop**:
  125. <p align="center">
  126. <img src="assets/evaluate-loop.png" alt="Evaluate-Loop: Plan, Evaluate Plan, Execute, Evaluate Execution, Fix or Complete" width="700"/>
  127. </p>
  128. | Step | What Happens |
  129. |------|-------------|
  130. | **Plan** | Breaks your goal into tasks with a dependency graph |
  131. | **Evaluate Plan** | Checks for scope issues, overlap with other work, and feasibility |
  132. | **Execute** | Writes code, runs tests, tracks progress — parallel when possible |
  133. | **Evaluate Execution** | Specialized checkers review UI/UX, code quality, integrations, and business logic |
  134. | **Fix** | Addresses any failures, then loops back to evaluation (up to 5 fix cycles; up to 3 plan revisions) |
  135. | **Complete** | All checks pass — track is marked done |
  136. The loop runs fully automated. It stops when the work passes all quality checks or when it needs your input.
  137. ### Parallel Execution
  138. When tasks don't depend on each other, they run simultaneously:
  139. <p align="center">
  140. <img src="assets/parallel-execution.png" alt="Parallel execution showing independent tasks running at the same time" width="700"/>
  141. </p>
  142. This means a feature with 6 tasks might only take as long as 3, because independent tasks run in parallel.
  143. ### Two Modes
  144. SupaConductor can work in two ways:
  145. | Mode | Behavior | Best For |
  146. |------|----------|----------|
  147. | **Agentic** (default) | Fully autonomous — makes all decisions itself | Experienced users who trust the system |
  148. | **Human-in-the-loop** | Pauses at key decision points to ask you | Learning the system, critical work, or when you want more control |
  149. Switch modes by editing `conductor/config.json` in your project:
  150. ```json
  151. { "mode": "agentic" }
  152. ```
  153. ```json
  154. { "mode": "human-in-the-loop" }
  155. ```
  156. ---
  157. ## Board of Directors
  158. 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:
  159. <p align="center">
  160. <img src="assets/board-of-directors.png" alt="Board of Directors: 5 executive perspectives deliberating on a decision" width="700"/>
  161. </p>
  162. | Director | Focus |
  163. |----------|-------|
  164. | **Chief Architect** | System design, scalability, technical debt |
  165. | **Chief Product Officer** | User value, market fit, feature scope |
  166. | **Chief Security Officer** | Vulnerabilities, compliance, data protection |
  167. | **Chief Operations Officer** | Feasibility, timelines, deployment risks |
  168. | **Chief Experience Officer** | UX/UI, accessibility, user journeys |
  169. Each director independently assesses your question, then they discuss and vote with written rationale.
  170. ```
  171. /orchestrator-supaconductor:board-meeting Should we migrate from REST to GraphQL?
  172. ```
  173. ```
  174. /orchestrator-supaconductor:board-review Add real-time notifications via WebSocket
  175. ```
  176. Use `board-meeting` for full deliberation (detailed, takes longer) or `board-review` for quick assessments.
  177. ---
  178. ## All Commands
  179. ### The Main Ones
  180. | Command | What It Does |
  181. |---------|-------------|
  182. | `/orchestrator-supaconductor:go <goal>` | Describe what you want — everything else is automatic |
  183. | `/orchestrator-supaconductor:setup` | Set up SupaConductor in your project (run once) |
  184. | `/orchestrator-supaconductor:status` | See all your tracks and their progress |
  185. | `/orchestrator-supaconductor:implement` | Continue the Evaluate-Loop on the current track |
  186. | `/orchestrator-supaconductor:new-track` | Create a new track with more manual control |
  187. ### Quality and Review
  188. | Command | What It Does |
  189. |---------|-------------|
  190. | `/orchestrator-supaconductor:phase-review` | Run a quality gate on completed work |
  191. | `/orchestrator-supaconductor:cto-advisor` | Get a CTO-level architecture review |
  192. | `/orchestrator-supaconductor:board-meeting <topic>` | Full board deliberation with voting |
  193. | `/orchestrator-supaconductor:board-review <topic>` | Quick board assessment |
  194. | `/orchestrator-supaconductor:ui-audit` | Accessibility and UI/UX review |
  195. ### Expert Advisors
  196. Ask for advice from virtual executives — they analyze your project and give guidance:
  197. | Command | Advisor |
  198. |---------|---------|
  199. | `/orchestrator-supaconductor:ceo` | Business strategy and product direction |
  200. | `/orchestrator-supaconductor:cmo` | Marketing strategy and positioning |
  201. | `/orchestrator-supaconductor:cto` | Technical architecture and engineering |
  202. | `/orchestrator-supaconductor:ux-designer` | User experience and design |
  203. ### Planning and Execution
  204. | Command | What It Does |
  205. |---------|-------------|
  206. | `/orchestrator-supaconductor:writing-plans` | Create a structured implementation plan |
  207. | `/orchestrator-supaconductor:executing-plans` | Execute an existing plan step by step |
  208. | `/orchestrator-supaconductor:brainstorming` | Creative exploration before building |
  209. | `/orchestrator-supaconductor:systematic-debugging` | Structured approach to finding and fixing bugs |
  210. | `/orchestrator-supaconductor:using-git-worktrees` | Isolate feature work in separate git worktrees |
  211. | `/orchestrator-supaconductor:finishing-a-development-branch` | Wrap up a branch — merge, PR, or cleanup |
  212. ### Loop Control (Advanced)
  213. These give you fine-grained control over individual loop steps:
  214. | Command | Step |
  215. |---------|------|
  216. | `/orchestrator-supaconductor:loop-planner` | Run just the planning step |
  217. | `/orchestrator-supaconductor:loop-plan-evaluator` | Evaluate just the plan |
  218. | `/orchestrator-supaconductor:loop-executor` | Run just the execution step |
  219. | `/orchestrator-supaconductor:loop-execution-evaluator` | Evaluate just the execution |
  220. | `/orchestrator-supaconductor:loop-fixer` | Run just the fix step |
  221. | `/orchestrator-supaconductor:parallel-dispatcher` | Dispatch parallel workers manually |
  222. | `/orchestrator-supaconductor:task-worker` | Run a single task from the plan |
  223. ---
  224. ## Architecture
  225. ### How the system fits together
  226. ```
  227. /go <your goal>
  228. |
  229. +----------v-----------+
  230. | Orchestrator |
  231. | (controls the loop) |
  232. +----------+-----------+
  233. |
  234. +-------------------+-------------------+
  235. v v v
  236. +--------+ +---------+ +----------+
  237. | Plan | ------> | Execute | ------> | Evaluate |
  238. +--------+ +---------+ +----------+
  239. | | |
  240. v v v
  241. writing-plans parallel-dispatcher 4 evaluators
  242. plan-evaluator |-- task-worker |-- eval-ui-ux
  243. cto-reviewer |-- task-worker |-- eval-code-quality
  244. +-- task-worker |-- eval-integration
  245. +-- eval-business-logic
  246. +----------------------+ +----------------------------+
  247. | Board of Directors | | Knowledge / Retrospective |
  248. | 5 directors + vote | | patterns.md + errors.json |
  249. +----------------------+ +----------------------------+
  250. ```
  251. ### What gets created in your project
  252. When you run `/orchestrator-supaconductor:setup`, it creates a `conductor/` folder:
  253. ```
  254. your-project/
  255. +-- conductor/
  256. |-- tracks.md # Registry of all your work tracks
  257. |-- config.json # Mode setting (agentic or human-in-the-loop)
  258. |-- workflow.md # How the development process works
  259. |-- authority-matrix.md # Who can make which decisions
  260. |-- decision-log.md # Record of architectural decisions
  261. |-- product.md # Product vision and requirements
  262. |-- tech-stack.md # Technology choices and constraints
  263. |-- knowledge/
  264. | |-- patterns.md # Patterns learned from completed work
  265. | +-- errors.json # Fixes for recurring errors
  266. +-- tracks/
  267. +-- feature-name/
  268. |-- spec.md # What needs to be built
  269. |-- plan.md # How to build it (tasks + dependencies)
  270. +-- metadata.json # Current state and configuration
  271. ```
  272. All of these are plain Markdown and JSON files. You can read, edit, or delete them anytime.
  273. ---
  274. ## FAQ
  275. ### Do I need to know how to code?
  276. You need one supported coding-agent host installed and basic terminal knowledge. Claude Code has the reference native integration; Codex, Cursor, Antigravity, Windsurf, and GitHub Copilot use generated platform adapters.
  277. ### How much does this cost in API credits?
  278. SupaConductor uses the same Claude API as normal Claude Code — it just structures the work more carefully. Because it runs multiple agents (planning, execution, evaluation), it uses roughly **3-5x** the API calls compared to doing everything manually in one conversation.
  279. SupaConductor optimizes costs automatically: it uses **Opus** (the most capable model) for planning and evaluation, and **Sonnet** (faster, cheaper) for execution tasks.
  280. Ways to reduce cost:
  281. - Use `/orchestrator-supaconductor:implement` if you write specs yourself
  282. - Skip board meetings for small features (they're opt-in)
  283. - Use human-in-the-loop mode to stay in control of scope
  284. ### How much of my context window does this use?
  285. Skills use **progressive disclosure** — only ~100 tokens each for metadata. Full instructions load only when activated (typically under 5,000 tokens each). The 39 skills are not loaded all at once.
  286. Agents run as **separate conversations** with their own context windows, so they don't fill up your main conversation.
  287. | Component | Context Used | When |
  288. |-----------|-------------|------|
  289. | Orchestrator | ~4,000 tokens | Active during `/go` |
  290. | Planner | ~3,000 tokens | During planning only |
  291. | Evaluator | ~2,500 tokens each | Only the active evaluator loads |
  292. | Board meeting | ~5,000 tokens | On-demand only |
  293. | Idle | ~500 tokens | Between steps |
  294. ### Does this work with Codex, Cursor, Windsurf, Antigravity, or Copilot?
  295. Yes. SupaConductor now ships generated adapters for **OpenAI Codex, Cursor, Google Antigravity, Windsurf/Cascade, and GitHub Copilot**, while preserving Claude Code as the reference integration.
  296. The hosts do not expose identical plugin APIs, so the adapter maps SupaConductor to each platform's strongest native primitives: Agent Skills, commands/workflows/prompts, and custom agents/subagents where supported. See [Platform Support](docs/platform-support.md) for the exact matrix.
  297. ### Is this overkill for small tasks?
  298. For a quick one-file fix — yes, just use Claude Code directly. Use SupaConductor when:
  299. - The work touches 3 or more files
  300. - You'd normally plan before coding
  301. - You want automated quality checks
  302. - You want the work done right the first time
  303. You can also use individual commands without the full loop:
  304. ```
  305. /orchestrator-supaconductor:board-review Should we use Redis or PostgreSQL for sessions?
  306. /orchestrator-supaconductor:cto-advisor
  307. /orchestrator-supaconductor:writing-plans
  308. ```
  309. ### Can I use this alongside other Claude Code plugins?
  310. Yes. SupaConductor uses the `/orchestrator-supaconductor:` namespace and doesn't conflict with any other plugins, built-in commands, or MCP servers.
  311. ### How do I update to a newer version?
  312. If you installed via the Claude Code marketplace:
  313. ```bash
  314. claude plugin marketplace update ibrahim-plugins
  315. claude plugin update orchestrator-supaconductor@ibrahim-plugins
  316. ```
  317. If you cloned via git:
  318. ```bash
  319. cd ~/.claude/plugins/orchestrator-supaconductor && git pull
  320. ```
  321. ### How do I uninstall?
  322. For a marketplace install:
  323. ```bash
  324. claude plugin uninstall orchestrator-supaconductor@ibrahim-plugins
  325. ```
  326. For a manual git clone:
  327. ```bash
  328. rm -rf ~/.claude/plugins/orchestrator-supaconductor
  329. ```
  330. The `conductor/` directory in your project stays — it's just documentation files.
  331. ---
  332. ## Migration from the Old Name
  333. If you previously installed `conductor-orchestrator-superpowers` (the old name):
  334. 1. Disable the old plugin: run `/plugin` in Claude Code and toggle it off
  335. 2. Delete the old folder: `rm -rf ~/.claude/plugins/conductor-orchestrator-superpowers`
  336. 3. Install SupaConductor using the [instructions above](#installation)
  337. 4. Run `/orchestrator-supaconductor:setup` in your existing projects to update references
  338. Your existing tracks and data are safe — only the command prefix changed from `/conductor:` to `/orchestrator-supaconductor:`.
  339. ---
  340. ## Community
  341. - [Discussions](https://github.com/Ibrahim-3d/orchestrator-supaconductor/discussions) — Questions, ideas, feedback, and what you've built
  342. - [Issues](https://github.com/Ibrahim-3d/orchestrator-supaconductor/issues) — Reproducible bugs and scoped actionable work
  343. - [Roadmap](ROADMAP.md) — Current direction, near-term priorities, and items under consideration
  344. - [Changelog](CHANGELOG.md) — Full version history
  345. - [Contributing](CONTRIBUTING.md) — Development and pull-request workflow
  346. - [Support](SUPPORT.md) — Where to ask for help
  347. ---
  348. ## Requirements
  349. - [Claude Code](https://docs.anthropic.com/en/docs/claude-code) CLI
  350. - Git
  351. ## Third-Party
  352. Bundles [Superpowers](https://github.com/obra/superpowers) v4.3.0 by [Jesse Vincent](https://github.com/obra), licensed under MIT. See [LICENSES/superpowers-MIT](LICENSES/superpowers-MIT).
  353. ## License
  354. SupaConductor is licensed under the **GNU Affero General Public License v3.0 (AGPL-3.0)** — see [LICENSE](LICENSE).
  355. Bundled third-party components retain their original licenses. Superpowers is MIT-licensed; see [LICENSES/superpowers-MIT](LICENSES/superpowers-MIT).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.