Skip to content
cccskills
FreePublished on GitHub

boardroom

Evaluate a strategic choice through multiple executive roles, each forming an independent view before discussion. Produce a board memo with recommendations, votes, dissent, risks, and success or stop conditions for the founder's decision.

OriginalShow the original description

/c-level-agents:boardroom [brief] — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.

See how to install

Good for

  • Reviewing a pricing change across business functions
  • Comparing fundraising with spending cuts
  • Gathering independent views from executive roles
  • Preparing a decision memo that preserves dissent

Files included (1)

  • SKILL.md4.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

/c-level-agents:boardroom — Multi-Role Boardroom Deliberation

Command: /c-level-agents:boardroom <brief-path>

Runs the board-meeting skill protocol across the C-suite for a single strategy brief. This is the heart of the plugin — the multi-role deliberation that gstack's review chain only approximates.

Pipeline Position

/c-level-agents:office-hours  →  /c-level-agents:brief  →  /c-level-agents:boardroom  →  /c-level-agents:decide  →  /c-level-agents:execute  →  /c-level-agents:post-mortem
                                     ↑ you are here

The 6 Phases (from board-meeting skill)

Phase 1 — Briefing

  • Chief of Staff distributes the brief to all advisors marked in Affected Roles.
  • Each advisor reads company-context.md + the brief.
  • No discussion yet.

Phase 2 — Independent Thinking (ISOLATION)

  • Critical: each advisor produces their position independently, without seeing others' positions.
  • This prevents groupthink and surfaces dissent.
  • Each writes: their voice's opening, recommendation, top 3 concerns, top 3 supports.

Phase 3 — Cross-Examination

  • Positions revealed simultaneously.
  • Each advisor critiques the others' positions on the dimensions they own:
    • cs-cfo-advisor critiques the math
    • cs-ciso-advisor critiques the risk
    • cs-cpo-advisor critiques the JTBD
    • cs-cmo-advisor critiques the positioning
    • cs-cro-advisor critiques the revenue math
    • etc.

Phase 4 — Devil's Advocate Pass

  • executive-mentor/devils-advocate agent runs /em:challenge on the leading option.
  • Surfaces three concerns with severity ratings.

Phase 5 — Synthesis

  • Chief of Staff synthesizes: which option commands majority, what are unresolved dissents.
  • Produces the board memo with recommendation + dissent.

Phase 6 — Decision Hand-off

  • Memo is presented to the founder.
  • Founder accepts, modifies, or rejects.
  • Approved memo routes to /c-level-agents:decide for logging.

Output: Board Memo

Saved to ~/.claude/boardroom/YYYY-MM-DD-<slug>.md:

# Board Memo: <topic>
**Date:** YYYY-MM-DD
**Brief:** <link to /c-level-agents:brief file>
**Status:** AWAITING FOUNDER DECISION | APPROVED | REJECTED

## Question
[One sentence from the brief]

## Recommended Option
**<Option name>** — chosen because <synthesis reasoning>

## Vote Tally
| Advisor | Vote | One-Sentence Reason |
|---|---|---|
| cs-ceo-advisor | A | <reason> |
| cs-cfo-advisor | A | <reason> |
| cs-cto-advisor | B | <reason> |
| ... | | |

## Dissent
- **<dissenter>:** <unresolved concern>

## Devil's Advocate Concerns
1. **CRITICAL** — <concern> — Mitigation: <plan>
2. **HIGH** — <concern> — Mitigation: <plan>
3. **MEDIUM** — <concern> — Mitigation: <plan>

## Success & Kill Criteria
[Copied from brief, refined by the panel]

## Recommended Decision Path
- `/c-level-agents:decide` → log the decision
- `/c-level-agents:execute` → 90-day plan
- `/c-level-agents:cross-eval` → multi-model sanity check (optional, high-stakes)
- `/c-level-agents:freeze N` → cooldown lock (optional, irreversible)

Why Phase 2 Isolation Matters

If advisors see each other's positions before forming their own, they anchor. Phase 2 isolation is the single highest-leverage practice in the board-meeting protocol — it surfaces the dissents that sycophancy would have suppressed.

Why This Beats gstack's Review Chain

gstack /autoplan/c-level-agents:boardroom
RolesCEO → design → eng (3)Up to 10 C-roles
OrderSequentialPhase 2 isolation, then simultaneous
Dissent captureImplicitExplicit dissent column
Adversarial passNoPhase 4 devil's advocate
OutputReviewed planVoted memo with dissent + kill criteria

Workflow

  1. Read brief from ~/.claude/briefs/<file>
  2. Identify affected roles
  3. Invoke each cs-* advisor independently (Phase 2)
  4. Collect positions
  5. Run cross-examination round (Phase 3)
  6. Run /em:challenge on leading option (Phase 4)
  7. Synthesize memo (Phase 5)
  8. Hand off to founder (Phase 6)

Routing

  • /c-level-agents:decide — log approved memo
  • /c-level-agents:cross-eval — high-stakes second opinion
  • /c-level-agents:freeze — cooldown lock

Related


Version: 1.0.0

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a11y-audit

FreeSummary

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

  • Audit a web application before release
  • Fix contrast and keyboard navigation issues
  • Prepare accessibility reports for stakeholders
alirezarezvani/claude-skills28.5KUpdated Oct 21, 2026

ab-test-setup

FreeSummary

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

  • Comparing landing page headlines
  • Testing signup button changes
  • Planning pricing page experiments
alirezarezvani/claude-skills28.5KUpdated Oct 21, 2026

ad-creative

FreeSummary

Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.

  • Creating Google RSA headlines
  • Writing Meta and LinkedIn ad copy
  • Developing variations of successful ads
alirezarezvani/claude-skills28.5KUpdated Oct 21, 2026

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

  • Reviewing a pull request before merging
  • Getting a second opinion on AI-written code
  • Checking authentication or data access code
alirezarezvani/claude-skills28.5KUpdated Oct 21, 2026

aeo

FreeSummary

Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.

  • Audit existing articles for evidence and credibility gaps
  • Revise article structure and references for AI answers
  • Record citations observed across AI services
alirezarezvani/claude-skills28.5KUpdated Oct 21, 2026

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

  • Creating signed records for production deployments
  • Preserving evidence of deletions and payments
  • Recording access grants for later review
alirezarezvani/claude-skills28.5KUpdated Oct 21, 2026

See all skills by alirezarezvani

Report a problem with this skill