Percerno Skillsbeta
← everything it can do · documents

Boardroom DOCX

Executes a 6-phase multi-role deliberation across C-suite advisors to analyze a strategy brief, producing a formal board memo with a vote tally, dissent notes, and devil's advocate concerns. It ensures independent thinking before cross-examination to prevent groupthink and surface critical risks.

7 uses this weeksource alirezarezvanilicence MIT
Quality gate: FAIL · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift -8.0 points (specificity, structure, method, fit).
won 0/2, lift -8.0, tokens ×64.45
Security scan: clean · 2026-10-24 · 1 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Kør boardroom-protokollen på briefet i ~/.claude/briefs/pricing-strategy.md.”
“Vi skal bestemme om vi skal skære budgettet eller rejse ny kapital. Indkald C-suiten til en fuldstændig drøftelse.”
“Tag briefet om indtræden på det europæiske marked og kør det gennem boardroom-processen for at få en stemt memo.”
“Run the boardroom protocol on the brief located at ~/.claude/briefs/2023-10-15-pricing-model.md.”
“We need to decide if we should cut runway or raise a Series B. Please convene the C-suite for a full deliberation on this trade-off.”
“Take the brief about entering the European market and run it through the multi-role boardroom process to get a voted memo.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

boardroomc-suitedeliberationstrategydecision-makingmulti-roleboard-memorisk-assessmentsynthesis

Not for

Do not use this for simple operational tasks, single-domain technical fixes, or routine project management updates. For finalizing the decision log or creating the 90-day execution plan, use the 'decide' or 'execute' skills instead. It is not for generating the initial strategy brief itself.

Details

When it is the right choice

Use this skill when a strategic decision impacts multiple executive domains, such as pricing, product, finance, and security simultaneously. It is ideal for high-stakes choices like raising capital, changing core business models, or major pivots where diverse perspectives are required. It is the correct step after a strategy brief has been drafted but before a final decision is logged.

The full recipe the assistant reads

/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
Roles CEO → design → eng (3) Up to 10 C-roles
Order Sequential Phase 2 isolation, then simultaneous
Dissent capture Implicit Explicit dissent column
Adversarial pass No Phase 4 devil's advocate
Output Reviewed plan Voted 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

Files in this skill (2)
  • LICENSE
  • SKILL.md
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-agents/skills/boardroom, licence MIT. The upstream licence file ships inside the skill.