Claude Skill

boardroom

Use for /c-level-agents:boardroom, or a decision spanning several executive domains (a pricing change, raise vs cut). Runs a 6-phase C-suite deliberation and writes a board memo.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download alirezarezvani-claude-skills-c-level-agents_skills_boardroom-9ef0c3c.zip · 2 KB

Install

skills CLI npx skills add https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/boardroom
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install alirezarezvani-claude-skills@llmmart
Git git clone https://github.com/alirezarezvani/claude-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole alirezarezvani/claude-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

/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 /executive-mentor: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 /executive-mentor: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 (claude-skills)
  • SKILL.md 4.7 KB
    ---
    name: "boardroom"
    description: "Use for /c-level-agents:boardroom, or a decision spanning several executive domains (a pricing change, raise vs cut). Runs a 6-phase C-suite deliberation and writes a board memo."
    ---
    
    # /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 `/executive-mentor: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`:
    
    ```markdown
    # 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 `/executive-mentor: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
    
    - Agent: [`cs-chief-of-staff`](../../agents/cs-chief-of-staff.md)
    - Skills: [`board-meeting`](${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/board-meeting/SKILL.md), [`executive-mentor`](${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/executive-mentor/executive-mentor/SKILL.md)
    
    ---
    
    **Version:** 1.0.0
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.