Guide · Agent skill
How to use the Boardroom Deliberation agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The boardroom skill makes an AI agent act like a panel of company executives who review one strategy brief, such as a pricing change or a raise-versus-cut runway call. It is useful for founders and small-company leaders who want a structured stress test of a decision that touches several functions, and for developers who want to study how multi-agent deliberation can be organized. By the end of this guide you will know how to install the skill, how to trigger it, what it needs to run, and how to read the board memo it produces.
Boardroom Deliberationalirezarezvani/claude-skills · MIT Download the skill Quick start
- 1Download the ZIP. Get the boardroom skill ZIP from the skill's page on this directory.
- 2Unzip into a skills folder. Unzip into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
- 3Install the required plugin parts. Make sure the c-level-agents plugin, its cs-* advisor agents, and the board-meeting and executive-mentor skills are available, since the workflow depends on them.
- 4Write a strategy brief. Save the decision, options and success and kill criteria as a file, typically under ~/.claude/briefs/.
- 5Run the deliberation. Invoke /c-level-agents:boardroom with the path to your brief, or ask the agent in plain language to run a boardroom review on that file.
- 6Review the board memo. Open the memo saved in ~/.claude/boardroom/, read the dissent and kill criteria, then accept, modify or reject it.
What an agent skill is and what the boardroom skill does
An agent skill is a folder with a SKILL.md file that gives an AI agent instructions for a specific task. The boardroom skill is one of these, and it is part of the c-level-agents plugin in the alirezarezvani/claude-skills repository.
The skill makes the agent run a six-phase deliberation. Each executive role (CEO, CFO, CTO, CISO, CMO and others) first forms its own position without seeing the others. Positions are then cross-examined, a devil's advocate pass looks for weak points in the leading option, and the agent synthesizes a board memo with a recommendation, a vote tally, dissenting opinions and kill criteria.
Install the boardroom skill
Download the ZIP file from the skill's page on this directory and unzip it. You can install it in one of two places: your personal skills folder at ~/.claude/skills/, or the .claude/skills/ folder inside a specific project.
If you use the Claude apps instead, you can upload the skill under Settings → Capabilities → Skills.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into the .claude/skills/ folder of your project
- Claude apps: Settings → Capabilities → Skills, then upload
Prepare a strategy brief before you run it
The skill works on a single strategy brief saved as a file, typically under ~/.claude/briefs/. The brief should state the decision, the options, and the success and kill criteria, since the memo copies these forward and the panel refines them.
Choose a decision that spans more than one function. The source notes the skill is meant for cases like a pricing change touching finance, positioning and product.
Trigger the skill with a request
The skill's command form is shown in the source as /c-level-agents:boardroom <brief-path>, where the argument is the path to your brief file. Because the description says to use it when a decision spans multiple executive domains, you can also describe the situation in natural language and point the agent to your brief file.
Examples of natural requests that match the skill's stated purpose:
- Run a boardroom review on ~/.claude/briefs/pricing-change.md
- Get the C-suite to deliberate on this raise-versus-cut runway brief and give me a board memo
- Stress test this pricing brief across finance, product and positioning before I decide
/c-level-agents:boardroom ~/.claude/briefs/pricing-change.mdRead the board memo
The output is saved to ~/.claude/boardroom/ with a date and slug in the filename. The memo has a status line (AWAITING FOUNDER DECISION, APPROVED or REJECTED), the question, the recommended option, a vote tally with one-sentence reasons, a dissent section, devil's advocate concerns graded CRITICAL, HIGH or MEDIUM with mitigations, and success and kill criteria.
The founder then accepts, modifies or rejects the memo. Per the source, an approved memo routes to /c-level-agents:decide for logging.
- Check the dissent section first; it lists the concerns that were not resolved.
- Review the kill criteria before acting on the recommendation.
- Treat the memo as AI-generated reasoning to be checked by qualified people.
What the skill needs and safety notes
The skill requires Claude Code or a compatible SKILL.md agent runtime, and the c-level-agents plugin with its cs-* advisor agents. It also relies on the board-meeting and executive-mentor skills and related commands. These are referenced but not included in the file reviewed, so the workflow may not run as described without them.
According to the review, the skill runs no scripts and uses no network access. Its output is reasoning rather than verified fact, and it is not suited to final decisions with legal, financial or safety consequences without review by qualified humans.
- Requires a strategy brief saved as a file
- Runs scripts: no
- Uses network: no
- Licence: MIT
Tips for better results
Write a brief that names the options clearly. A panel can only vote on options it can see, and a vague brief produces a vague memo.
Use the skill for multi-function decisions. For a simple or single-domain question, a multi-role panel adds cost and little value.
- Include concrete numbers in the brief so the finance and revenue roles have something to test.
- Define kill criteria up front so the memo can refine them rather than invent them.
- Use /c-level-agents:cross-eval for a second opinion on high-stakes decisions, as the memo's routing section suggests.
What people use it for
- Testing a pricing change that affects finance, positioning and product at the same time.
- Working through a raise-versus-cut runway decision with the finance and revenue perspectives visible.
- Recording dissenting opinions alongside a recommendation for a small leadership team.
- Studying how a multi-agent deliberation protocol with isolated first-round positions can be structured.
Frequently asked questions
Is the boardroom skill free to use?
The source states the skill is released under the MIT licence. It does not mention pricing for the skill itself, and it depends on Claude Code or a compatible runtime, which may have its own terms.
What do I need before I can run the boardroom skill?
You need Claude Code or a compatible SKILL.md runtime, the c-level-agents plugin with its cs-* advisor agents, the board-meeting and executive-mentor skills, and a strategy brief saved as a file. The source says the sibling skills and commands are not included in the file reviewed.
Where do I install the boardroom skill?
Unzip the downloaded ZIP into ~/.claude/skills/ for personal use, or into the .claude/skills/ folder of a project. In the Claude apps, you can upload it under Settings → Capabilities → Skills.
Does the boardroom skill run scripts or use the internet?
According to the review, it runs no scripts and uses no network access. It does rely on a strategy brief file and on referenced plugin components.
What is Phase 2 isolation and why does it matter?
In Phase 2 each advisor forms a position without seeing the others, which the source says prevents anchoring and surfaces dissent that groupthink would hide. The skill then reveals positions simultaneously in Phase 3.
How is this different from gstack's review chain?
The source compares gstack's /autoplan, a sequential review of CEO, design and engineering, with the boardroom skill, which uses up to ten C-roles, isolated first positions, an explicit dissent column, a devil's advocate phase and a voted memo with kill criteria.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
The boardroom skill suits founders and small teams who want a structured, written stress test of a decision that spans several functions, and developers studying multi-agent deliberation. It is a poor fit for single-domain questions, for final legal, financial or safety decisions without qualified review, and for anyone without the referenced sibling skills and plugin files, since the workflow may not run as described without them.
Download the skill