Agent skill

Board Of Directors

by Ibrahim-3d in Ibrahim-3d/orchestrator-supaconductor

Simulate a 5-member expert board deliberation for major decisions.

AGPL-3.0Auto-check passed

Install Board Of Directors

skills CLI
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill board-of-directors -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Ibrahim-3d/orchestrator-supaconductor board-of-directors --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/board-of-directors .claude/skills/board-of-directors && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
board-of-directors
GitHub stars
381
Token cost
~1.9k tokens
SKILL.md length
361 words
Files
6
Skills in repo
27
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Simulate a 5-member expert board deliberation for major decisions.

  • Works in 5 steps: Individual Assessment (Parallel) → Board Discussion (Sequential via Message… → Final Vote → …
  • Evaluating plans
  • SKILL.md covers The Board, When to Invoke the Board, Deliberation Protocol and Orchestrator Integration, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Board Of Directors is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Simulate a 5-member expert board deliberation for major decisions. Use when evaluating plans, architecture choices, feature designs, or any decision requiring multi-perspective expert analysis. Triggers: 'board review', 'get expert opinions', 'board meeting', 'director evaluation', 'consensus review'.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `directors/chief-architect.md`, `directors/chief-experience-officer.md` and `directors/chief-operations-officer.md`).

The repository describes itself as: Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. The licence is AGPL-3.0.

When your agent uses it

  • Evaluating plans
  • Architecture choices
  • Feature designs
  • Any decision requiring multi-perspective expert analysis

Example prompts

  • “board review”
  • “get expert opinions”
  • “board meeting”
  • “/board-of-directors”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Individual Assessment (Parallel)
  2. Board Discussion (Sequential via Message Bus)
  3. Final Vote
  4. Board Resolution
  5. Persist Decision (MANDATORY)

What it can do on your machine

Read from SKILL.md and the folder at commit 76c9b10. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json, markdown and typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Board Of Directors loads about 1.9k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 361 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 361 words, ~1,897 tokens.

Download SKILL.mdSave it as .claude/skills/board-of-directors/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
board-of-directors
description
Simulate a 5-member expert board deliberation for major decisions. Use when evaluating plans, architecture choices, feature designs, or any decision requiring multi-perspective expert analysis. Triggers: 'board review', 'get expert opinions', 'board meeting', 'director evaluation', 'consensus review'.

Board of Directors Simulation

Simulates a 5-member expert board that deliberates, debates, and reaches consensus on major decisions. Each director brings domain expertise and can challenge other directors' opinions.

The Board

RoleDomainEvaluates
Chief Architect (CA)TechnicalSystem design, patterns, scalability, tech debt, code quality
Chief Product Officer (CPO)ProductUser value, market fit, feature priority, scope, usability
Chief Security Officer (CSO)SecurityVulnerabilities, compliance, data protection, risk assessment
Chief Operations Officer (COO)ExecutionFeasibility, timeline, resources, process, deployment
Chief Experience Officer (CXO)ExperienceUX/UI, accessibility, user journey, design consistency

When to Invoke the Board

  • Track Planning — Before starting major tracks
  • Architecture Decisions — ADRs, system design choices
  • Feature Evaluation — New feature proposals
  • Risk Assessment — Security or operational concerns
  • Conflict Resolution — When leads disagree

Deliberation Protocol

Phase 1: Individual Assessment (Parallel)

Each director reviews the proposal independently:

DISPATCH via Task tool (all 5 in parallel):
  - CA: Evaluate technical aspects
  - CPO: Evaluate product aspects
  - CSO: Evaluate security aspects
  - COO: Evaluate operational aspects
  - CXO: Evaluate experience aspects

Each director outputs:

json
{
  "director": "CA",
  "verdict": "APPROVE" | "CONCERNS" | "REJECT",
  "score": 1-10,
  "key_points": ["..."],
  "concerns": ["..."],
  "questions_for_board": ["Question for CPO about...", "Challenge to COO on..."]
}
Phase 2: Board Discussion (Sequential via Message Bus)

Directors respond to each other's questions and challenges:

MESSAGE BUS: conductor/tracks/{track}/.message-bus/board/

1. Post all Phase 1 assessments to board/assessments.json
2. Each director reads others' assessments
3. Directors post rebuttals/responses to board/discussion.jsonl
4. Max 3 rounds of discussion

Discussion message format:

json
{
  "from": "CA",
  "to": "CPO",
  "type": "CHALLENGE" | "AGREE" | "QUESTION" | "CLARIFY",
  "message": "Regarding your concern about scope...",
  "changes_my_verdict": true | false
}
Phase 3: Final Vote

After discussion, each director casts final vote:

json
{
  "director": "CA",
  "final_verdict": "APPROVE" | "REJECT",
  "confidence": 0.0-1.0,
  "conditions": ["Must add rate limiting", "Needs load testing"],
  "dissent_noted": false
}
Phase 4: Board Resolution

Aggregate votes and produce board decision:

ScenarioResolution
5-0 or 4-1 APPROVEAPPROVED — Proceed with any conditions noted
3-2 APPROVEAPPROVED WITH REVIEW — Proceed but schedule follow-up
3-2 REJECTREJECTED — Address major concerns first
4-1 or 5-0 REJECTREJECTED — Significant rework needed
2-2-1 (tie with abstain)Chief Architect (CA) casts tiebreaking vote based on technical merit
Show full SKILL.md (137 more words)Show less
Phase 5: Persist Decision (MANDATORY)

After reaching resolution, you MUST persist the decision to files:

  1. Create directory: Use run_shell_command mkdir -p conductor/tracks/{trackId}/.message-bus/board/
  2. write_file resolution.md with the Board Output Format (below)
  3. write_file session-{timestamp}.json:
    json
    {"session_id": "...", "verdict": "...", "vote_summary": {...}, "conditions": [...], "timestamp": "..."}

Then return ONLY this concise summary to the orchestrator:

json
{"verdict": "APPROVED|REJECTED|ESCALATE", "conditions": ["..."], "vote": "4-1"}

Orchestrator Integration

Invoke Board from Conductor
typescript
async function invokeBoardReview(proposal: string, context: object) {
  // 1. Initialize board message bus
  await initBoardMessageBus(trackId);

  // 2. Phase 1: Parallel assessment
  const assessments = await Promise.all([
    Task({
      description: "CA board assessment",
      prompt: `You are the Chief Architect on the Board of Directors.

        PROPOSAL: ${proposal}
        CONTEXT: ${JSON.stringify(context)}

        Follow the directors/chief-architect.md profile.

        Output your assessment as JSON.`
    }),
    Task({ description: "CPO board assessment", ... }),
    Task({ description: "CSO board assessment", ... }),
    Task({ description: "COO board assessment", ... }),
    Task({ description: "CXO board assessment", ... })
  ]);

  // 3. Phase 2: Discussion rounds
  await runBoardDiscussion(assessments, maxRounds: 3);

  // 4. Phase 3: Final vote
  const votes = await collectFinalVotes();

  // 5. Phase 4: Resolution
  return aggregateBoardDecision(votes);
}
Board Output Format
markdown
## Board of Directors Resolution

**Proposal**: [Brief description]
**Session**: [timestamp]
**Verdict**: APPROVED | APPROVED WITH REVIEW | REJECTED | ESCALATE

### Vote Summary
| Director | Vote | Confidence | Key Condition |
|----------|------|------------|---------------|
| CA | APPROVE | 0.9 | Add caching layer |
| CPO | APPROVE | 0.8 | Validate with usability check |
| CSO | CONCERNS→APPROVE | 0.7 | Security audit before launch |
| COO | APPROVE | 0.85 | Need 2-week buffer |
| CXO | APPROVE | 0.95 | Accessibility is solid |

**Final: 5-0 APPROVE**

### Conditions for Approval
1. Add caching layer for API responses (CA)
2. Complete security audit before production (CSO)
3. Buffer timeline by 2 weeks (COO)

### Discussion Highlights
- CA challenged CPO on scope creep → CPO agreed to defer Phase 2
- CSO raised auth concern → CA proposed token rotation solution
- CXO praised accessibility approach, no concerns

### Dissenting Opinions
None recorded.

---
*Board session complete. Proceed with implementation.*

Director Skills

Each director has specialized evaluation criteria. See:

  • directors/chief-architect.md — Technical excellence
  • directors/chief-product-officer.md — Product value
  • directors/chief-security-officer.md — Security posture
  • directors/chief-operations-officer.md — Execution reality
  • directors/chief-experience-officer.md — User experience

Quick Invocation

For rapid board review without full deliberation:

markdown
/board-review [proposal]

Returns: Quick assessment from each director (no discussion phase)

For full deliberation:

markdown
/board-meeting [proposal]

Returns: Full 4-phase deliberation with discussion

Integration with Evaluate-Loop

The board can be invoked at key checkpoints:

CheckpointBoard Involvement
EVALUATE_PLANFull board meeting for major tracks
EVALUATE_EXECUTIONQuick review for implementation quality
Pre-LaunchSecurity + Operations deep dive
Post-MortemAll directors analyze what went wrong

Message Bus Structure

.message-bus/board/
├── session-{timestamp}.json    # Session metadata
├── assessments.json            # Phase 1 outputs
├── discussion.jsonl            # Phase 2 messages
├── votes.json                  # Phase 3 final votes
└── resolution.md               # Phase 4 board decision

© Ibrahim-3d, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files in skills/board-of-directors of Ibrahim-3d/orchestrator-supaconductor.

  • SKILL.md
  • directors/chief-architect.md
  • directors/chief-experience-officer.md
  • directors/chief-operations-officer.md
  • directors/chief-product-officer.md
  • directors/chief-security-officer.md

Open the folder on GitHubat commit 76c9b10

Compare with similar skills

Board Of Directors next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Board Of Directors compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Board Of Directors this skillIbrahim-3d/orchestrator-supaconductor381—~1.9kAutomated safety check: PassAGPL-3.0
Boardalirezarezvani/claude-skills28k—~610Automated safety check: PassMIT
Paperclip Boardpaperclipai/paperclip100k—~5.3kAutomated safety check: PassMIT
Creative Directornexu-io/open-design100k—~715Automated safety check: PassApache-2.0
Personal Board Of Directorsmohitagw15856/pm-claude-skills1.4k—~1kAutomated safety check: PassMIT
Eas Simulatorsickn33/agentic-awesome-skills47k1 repos~6kAutomated safety check: NotesMIT

Similar skills

  • Board

    alirezarezvani/claude-skills

    Read, write, and browse the AgentHub message board for agent coordination.

    28k GitHub stars~610 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Paperclip Board

    paperclipai/paperclip

    Manage a Paperclip company as a board member via chat. An agent skill from paperclipai/paperclip.

    100k GitHub stars~5.3k tokensUpdated today
    Auto-check passed
  • Creative Director

    nexu-io/open-design

    AI creative director with recursive self-assessment: 20+ methodologies (SIT, TRIZ, Bisociation, SCAMPER, Synectics), 3-axis evaluation calibrated against Cannes/D&AD/HumanKind, 5-phase process from…

    100k GitHub stars~715 tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Personal Board Of Directors

    mohitagw15856/pm-claude-skills

    Five standing advisors — the Operator, the Skeptic, the CFO, the Coach, the Customer — debate your decision on paper and vote.

    1.4k GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed
  • Eas Simulator

    sickn33/agentic-awesome-skills

    Curated upstream guidance for Eas Simulator; use when the workflow matches the user goal.

    47k GitHub starsUsed in 1 repo~6k tokens
    MobileAuto-check: notes
  • Board Governance

    sickn33/agentic-awesome-skills

    Board and governance register: meeting date, agenda, decision, resolution number, vote result, action owner and due date.

    47k GitHub starsUsed in 1 repo~4.1k tokens
    Auto-check passed

More from Ibrahim-3d/orchestrator-supaconductor

All 27 skills in this repo
  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    Auto-check passed
  • Context Driven Development

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…

    381 GitHub starsUsed in 9 repos~2.9k tokens
    Auto-check passed
  • Agent Factory

    Ibrahim-3d/orchestrator-supaconductor

    Creates specialized worker agents dynamically from templates.

    381 GitHub stars~2.9k tokensUpdated 13 days ago
    Auto-check passed
  • Business Docs Sync

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.

    381 GitHub stars~2.1k tokensUpdated 13 days ago
    Auto-check passed
  • Context Loader

    Ibrahim-3d/orchestrator-supaconductor

    Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

    381 GitHub stars~830 tokensUpdated 13 days ago
    Auto-check passed
  • Eval Business Logic

    Ibrahim-3d/orchestrator-supaconductor

    Specialized business logic evaluator for the Evaluate-Loop. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

    381 GitHub stars~1.6k tokensUpdated 13 days ago
    Auto-check passed

Questions about Board Of Directors

What does Board Of Directors do?

Simulate a 5-member expert board deliberation for major decisions. Board Of Directors is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Simulate a 5-member expert board deliberation for major decisions.

When should I use Board Of Directors?

Board Of Directors fits situations like: evaluating plans; architecture choices; feature designs; any decision requiring multi-perspective expert analysis.

How do I install Board Of Directors in Claude Code?

Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill board-of-directors -a claude-code`. Or copy the skill folder (skills/board-of-directors in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/board-of-directors in your project. Claude Code loads it when a task matches its description.

How do I install Board Of Directors in Codex?

Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill board-of-directors -a codex`. Or copy the skill folder (skills/board-of-directors in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/board-of-directors in your project. Codex loads it when a task matches its description.

Can I use Board Of Directors in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill board-of-directors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/board-of-directors, .gemini/skills/board-of-directors, .github/skills/board-of-directors and .opencode/skills/board-of-directors in your project.

What does Board Of Directors need to run?

SKILL.md names no scripts, command-line tools or credentials: Board Of Directors is instructions for the agent only.

Does Board Of Directors access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Board Of Directors safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Board Of Directors use?

Board Of Directors is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Board Of Directors use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Board Of Directors?

Skills that share tags, products or a category with Board Of Directors: Board (alirezarezvani/claude-skills, 28k stars), Paperclip Board (paperclipai/paperclip, 100k stars), Creative Director (nexu-io/open-design, 100k stars) and Personal Board Of Directors (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Board Of Directors?

Ibrahim-3d (a GitHub user) maintains it in Ibrahim-3d/orchestrator-supaconductor, which has 381 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 27, 2026.

Source: Ibrahim-3d/orchestrator-supaconductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.