Question 1

How do I update to a newer version?

Accepted Answer

If you installed via marketplace: (instructions omitted). If you cloned via git: (instructions omitted).

Question 2

Can I use this alongside other Claude Code plugins?

Accepted Answer

Yes. SupaConductor uses the /orchestrator-supaconductor: namespace and doesn't conflict with any other plugins, built‑in commands, or MCP servers.

Question 3

Does this work with Cursor, Windsurf, or other AI tools?

Accepted Answer

No — SupaConductor is a Claude Code plugin that requires Claude Code's plugin system (agents, skills, slash commands, hooks). However, the conductor/ directory it creates is just Markdown files, so any AI tool can read them. You can start with SupaConductor and later switch tools while keeping your specs, plans, and documentation.

Question 4

How much of my context window does this use?

Accepted Answer

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. Agents run as separate conversations with their own context windows, so they don't fill up your main conversation. Context usage per component: Orchestrator ~4,000 tokens (active during /go); Planner ~3,000 tokens (during planning only); Evaluator ~2,500 tokens each (only when active); Board meeting ~5,000 tokens (on‑demand); Idle ~500 tokens (between steps).

Question 5

Is this overkill for small tasks?

Accepted Answer

For a quick one‑file fix, yes, just use Claude Code directly. Use SupaConductor when the work touches three or more files, you would normally plan before coding, you want automated quality checks, or you want the work done right the first time. You can also use individual commands without the full loop.

Question 6

How much does this cost in API credits?

Accepted Answer

SupaConductor uses the same Claude API as normal Claude Code, but runs multiple agents (planning, execution, evaluation), so it uses roughly 3–5× the API calls compared to doing everything manually in one conversation. It optimizes costs automatically: Opus (most capable) for planning and evaluation, Sonnet (faster, cheaper) for execution tasks. Ways to reduce cost: use /orchestrator-supaconductor:implement if you write specs yourself, skip board meetings for small features (opt‑in), or use human‑in‑the‑loop mode to stay in control of scope.

Question 7

Do I need to know how to code?

Accepted Answer

You need Claude Code installed and running, which requires basic terminal knowledge. Once SupaConductor is set up, you describe what you want in plain English and it handles the implementation.

Question 8

How does it work?

Accepted Answer

Every piece of work follows a structured cycle called the Evaluate-Loop: Plan – breaks your goal into tasks with a dependency graph; Evaluate Plan – checks for scope issues, overlap, 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 (up to 5 fix cycles, up to 3 plan revisions); Complete – all checks pass and the track is marked done. The loop runs fully automated and stops when work passes all quality checks or needs your input.

Question 9

What gets created in my project?

Accepted Answer

When you run /orchestrator-supaconductor:setup, it creates a conductor/ folder containing plain Markdown and JSON files. You can read, edit, or delete them anytime.

Question 10

What's inside?

Accepted Answer

Component list: Commands (36) – slash commands to control everything; Skills (39) – specialized knowledge modules; Agents (15) – autonomous workers for planning, coding, and evaluation; Evaluators (4) – quality checkers for UI/UX, code quality, integrations, and business logic; Board of Directors (5) – virtual executives for 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.

Question 11

What does this do?

Accepted Answer

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, manually reviewing, re-prompting, and fixing what it misses. With SupaConductor, you type one command 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.

Question 12

What's New in v3.7.0?

Accepted Answer

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.

Aperçu

Fonctionnalités clés

Tarifs

Cas d’usage

Commencer à travailler sur une nouvelle piste

Mettre en œuvre des fonctionnalités

Avoir besoin du contexte du projet

Pour & contre

Pour

Contre

Avis

Questions & réponses

Poser une question

Alternatives à Compétences

Manage Headers (Grade A)

Using Git Worktrees (Grade A)

Ga4 Bigquery Schema (Grade A)

Meta Capi (Grade A)

Callees (Grade A)

Test Module Name (Grade A)

Board Of Directors (Grade A)

Advpl Mvc Avancado (Grade A)