Executive Boardroom Deliberator

/cs:boardroom — Multi-Role Boardroom Deliberation

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo.

---
name: "boardroom"
description: "/cs: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."
---

# /cs:boardroom — Multi-Role Boardroom Deliberation

**Command:** `/cs: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

```
/cs:office-hours  →  /cs:brief  →  /cs:boardroom  →  /cs:decide  →  /cs:execute  →  /cs:post-mortem
                                     ↑ you are here
```

Overview

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.

Manual install (npx, ZIP)

Claude Codenpx skills add alirezarezvani/claude-skills --skill boardroom -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \
  | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/c-level-agents/skills/boardroom

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/e35c764b3d9ac8124352/boardroom.zip" -OutFile "$env:TEMP\boardroom.zip"; Expand-Archive "$env:TEMP\boardroom.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md4.6 KB

Read the files here

alirezarezvani/19392f71 file

SKILL.md4.6 KB

Shared references15SKILL.md reads these from elsewhere in the repo. Not in the ZIP.

Get them on GitHub ↗

SKILL.md

Show the full text135 lines

boardroom/SKILL.md135 lines · 4.6 KB

PreviewCode

Outline

RawView on GitHub

/cs:boardroom — Multi-Role Boardroom Deliberation

Command: /cs: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

/cs:office-hours  →  /cs:brief  →  /cs:boardroom  →  /cs:decide  →  /cs:execute  →  /cs: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 /cs: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 /cs: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
- `/cs:decide` → log the decision
- `/cs:execute` → 90-day plan
- `/cs:cross-eval` → multi-model sanity check (optional, high-stakes)
- `/cs: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`	`/cs: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

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

Routing

/cs:decide — log approved memo
/cs:cross-eval — high-stakes second opinion
/cs:freeze — cooldown lock

Agent: cs-chief-of-staff
Skills: board-meeting, executive-mentor

Version: 1.0.0

1	---
2	name: "boardroom"
3	description: "/cs: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."
4	---
5
6	# /cs:boardroom — Multi-Role Boardroom Deliberation
7
8	Command: `/cs:boardroom <brief-path>`
9
10	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.
11
12	## Pipeline Position
13
14	```
15	/cs:office-hours → /cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortem
16	↑ you are here
17	```
18
19	## The 6 Phases (from board-meeting skill)
20
21	### Phase 1 — Briefing
22	- Chief of Staff distributes the brief to all advisors marked in Affected Roles.
23	- Each advisor reads company-context.md + the brief.
24	- No discussion yet.
25
26	### Phase 2 — Independent Thinking (ISOLATION)
27	- Critical: each advisor produces their position independently, without seeing others' positions.
28	- This prevents groupthink and surfaces dissent.
29	- Each writes: their voice's opening, recommendation, top 3 concerns, top 3 supports.
30
31	### Phase 3 — Cross-Examination
32	- Positions revealed simultaneously.
33	- Each advisor critiques the others' positions on the dimensions they own:
34	- cs-cfo-advisor critiques the math
35	- cs-ciso-advisor critiques the risk
36	- cs-cpo-advisor critiques the JTBD
37	- cs-cmo-advisor critiques the positioning
38	- cs-cro-advisor critiques the revenue math
39	- etc.
40
41	### Phase 4 — Devil's Advocate Pass
42	- `executive-mentor/devils-advocate` agent runs `/em:challenge` on the leading option.
43	- Surfaces three concerns with severity ratings.
44
45	### Phase 5 — Synthesis
46	- Chief of Staff synthesizes: which option commands majority, what are unresolved dissents.
47	- Produces the board memo with recommendation + dissent.
48
49	### Phase 6 — Decision Hand-off
50	- Memo is presented to the founder.
51	- Founder accepts, modifies, or rejects.
52	- Approved memo routes to `/cs:decide` for logging.
53
54	## Output: Board Memo
55
56	Saved to `~/.claude/boardroom/YYYY-MM-DD-<slug>.md`:
57
58	```markdown
59	# Board Memo: <topic>
60	Date: YYYY-MM-DD
61	Brief: <link to /cs:brief file>
62	Status: AWAITING FOUNDER DECISION \| APPROVED \| REJECTED
63
64	## Question
65	[One sentence from the brief]
66
67	## Recommended Option
68	<Option name> — chosen because <synthesis reasoning>
69
70	## Vote Tally
71	\| Advisor \| Vote \| One-Sentence Reason \|
72	\|---\|---\|---\|
73	\| cs-ceo-advisor \| A \| <reason> \|
74	\| cs-cfo-advisor \| A \| <reason> \|
75	\| cs-cto-advisor \| B \| <reason> \|
76	\| ... \| \| \|
77
78	## Dissent
79	- <dissenter>: <unresolved concern>
80
81	## Devil's Advocate Concerns
82	1. CRITICAL — <concern> — Mitigation: <plan>
83	2. HIGH — <concern> — Mitigation: <plan>
84	3. MEDIUM — <concern> — Mitigation: <plan>
85
86	## Success & Kill Criteria
87	[Copied from brief, refined by the panel]
88
89	## Recommended Decision Path
90	- `/cs:decide` → log the decision
91	- `/cs:execute` → 90-day plan
92	- `/cs:cross-eval` → multi-model sanity check (optional, high-stakes)
93	- `/cs:freeze N` → cooldown lock (optional, irreversible)
94	```
95
96	## Why Phase 2 Isolation Matters
97
98	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.
99
100	## Why This Beats gstack's Review Chain
101
102	\| \| gstack `/autoplan` \| `/cs:boardroom` \|
103	\|---\|---\|---\|
104	\| Roles \| CEO → design → eng (3) \| Up to 10 C-roles \|
105	\| Order \| Sequential \| Phase 2 isolation, then simultaneous \|
106	\| Dissent capture \| Implicit \| Explicit dissent column \|
107	\| Adversarial pass \| No \| Phase 4 devil's advocate \|
108	\| Output \| Reviewed plan \| Voted memo with dissent + kill criteria \|
109
110	## Workflow
111
112	1. Read brief from `~/.claude/briefs/<file>`
113	2. Identify affected roles
114	3. Invoke each cs-* advisor independently (Phase 2)
115	4. Collect positions
116	5. Run cross-examination round (Phase 3)
117	6. Run `/em:challenge` on leading option (Phase 4)
118	7. Synthesize memo (Phase 5)
119	8. Hand off to founder (Phase 6)
120
121	## Routing
122
123	- `/cs:decide` — log approved memo
124	- `/cs:cross-eval` — high-stakes second opinion
125	- `/cs:freeze` — cooldown lock
126
127	## Related
128
129	- Agent: [`cs-chief-of-staff`](../../agents/cs-chief-of-staff.md)
130	- Skills: [`board-meeting`](../../../c-level-advisor/skills/board-meeting/SKILL.md), [`executive-mentor`](../../../c-level-advisor/executive-mentor/)
131
132	---
133
134	Version: 1.0.0
135