One paragraph describing what this agent does, who it's for, and when to activate it.
board-meeting
board-meeting is an open-source integrations skill for Claude Code and compatible agents, published by alirezarezvani. Its author describes it as: “Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, foun…”. The project has 25k stars on GitHub and is available under the MIT license. Add it to your setup with `/plugin marketplace add alirezarezvani/claude-skills`.
What board-meeting does
Structured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.
Installation
Add board-meeting to your agent with:
/plugin marketplace add alirezarezvani/claude-skillsAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for board-meeting is organised into these sections:
- Keywords
- Invoke
- The 6-Phase Protocol
- PHASE 1: Context Gathering
- PHASE 2: Independent Contributions (ISOLATED)
- PHASE 3: Critic Analysis
- PHASE 4: Synthesis
- PHASE 5: Human in the Loop ⏸️
- PHASE 6: Decision Extraction
- Memory Structure
- Failure Mode Quick Reference
- References
When to use it
Reach for board-meeting when you want integrations help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear MIT license — safe to read and adapt
- Ships in alirezarezvani/claude-skills, an established project with 24,617 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does board-meeting do?
- Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
- How do I install board-meeting?
- Run /plugin marketplace add alirezarezvani/claude-skills in your agent, then reload your skills. Review the source at https://github.com/alirezarezvani/claude-skills before installing.
- Is board-meeting free to use?
- Yes. board-meeting is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
- Where does board-meeting come from?
- board-meeting ships inside alirezarezvani/claude-skills, a repository that contains 41 catalogued skills in total. The repository's 24,617 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Integrations →Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
Mint a tamper-evident, post-quantum-signed receipt for a consequential agent action (deploy, delete, pay, grant-access, model decision) so it can be verified later from the certificate alone. Use when an autonomous agent takes a side-effecting action that may need to be proven later, or when satisfying EU AI Act Article 12 record-keeping. Three decisions: whether an action needs a receipt, minting it, verifying it. Signing is delegated to the open-source OpenAgentOntology package. Not after-the-fact log analysis; not a hosted notary; not a legal opinion.
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.