Question 1

How do I update to a newer version?

Accepted Answer

If you installed via marketplace: If you cloned via git:

Question 2

Are there any drawbacks to using this tool?

Accepted Answer

The process can be time-consuming due to the multiple phases involved, and requires careful setup and coordination to ensure effective use.

Question 3

What are the benefits of using this tool?

Accepted Answer

The Board of Directors skill provides multi-perspective expert analysis for informed decision-making and simulates a thorough deliberation process to ensure well-considered decisions.

Question 4

How does the deliberation process work?

Accepted Answer

The deliberation process involves individual assessments, board discussions, and a final vote to reach a consensus. Each director reviews the proposal independently, then responds to each other's questions and challenges, and finally casts a final vote.

Question 5

What roles are included?

Accepted Answer

The Board of Directors skill includes five roles: Chief Architect (CA), Chief Product Officer (CPO), Chief Security Officer (CSO), Chief Operations Officer (COO), and Chief Experience Officer (CXO).

Question 6

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 7

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 3 or more files; You'd normally plan before coding; You want automated quality checks; You want the work done right the first time. You can also use individual commands without the full loop.

Question 8

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. Any AI tool can read them. If you start with SupaConductor and switch tools later, your specs, plans, and documentation remain useful.

Question 9

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. | Component | Context Used | When | |-----------|-------------|------| | Orchestrator | ~4,000 tokens | Active during /go | | Planner | ~3,000 tokens | During planning only | | Evaluator | ~2,500 tokens each | Only the active evaluator loads | | Board meeting | ~5,000 tokens | On-demand only | | Idle | ~500 tokens | Between steps |

Question 10

How much does this cost in API credits?

Accepted Answer

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. SupaConductor optimizes costs automatically: it uses Opus (the most capable model) for planning and evaluation, and 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 (they're opt-in); Use human-in-the-loop mode to stay in control of scope.

Question 11

Do I need to know how to code?

Accepted Answer

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

Question 12

How It Works?

Accepted Answer

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.

Question 13

What gets created in your project?

Accepted Answer

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

Question 14

What's Inside?

Accepted Answer

| 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.

Question 15

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. You manually review, re-prompt, and fix 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. Just describe what you want and walk away.

Question 16

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.

Board Of Directors (Grade A)Security-tested data-ai skill for Claude AI. Grade A. Simulate a 5-member expert board deliberation for major decisions. Use when evaluating plans, architecture choices, feature designs, or any decisi

Overview

Key features

Pricing

Use cases

Evaluating Major Architectural Decisions

Feature Design Review

Risk Assessment and Mitigation

Pros & Cons

Pros

Cons

Reviews

Q&A

Ask a question

Skills alternatives