C Level Advisor
- 1.8k installs
- 23.5k repo stars
- Updated July 17, 2026
- alirezarezvani/claude-skills
boardroom is an agent skill that /cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, an.
About
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 cs office hours cs brief cs boardroom cs decide cs execute cs post mortem you are here The 6 Phases from board meeting skill The boardroom agent skill provides documented workflows prerequisites triggers and safety guidance from its SKILL md source Agents load it when user requests match the description and follow step by step instructions without inventing capabilities It integrates with standard agent tooling for the tasks inputs outputs and failure modes described in the repository documentation
- description: "/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic
- **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 plugi
- Follow boardroom SKILL.md steps and documented constraints.
- Follow boardroom SKILL.md steps and documented constraints.
C Level Advisor by the numbers
- 1,814 all-time installs (skills.sh)
- Ranked #271 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
c-level-advisor capabilities & compatibility
- Capabilities
- description: "/cs:boardroom <brief> — 6 phase mu · **command:** `/cs:boardroom <brief path>` · runs the `board meeting` skill protocol across t · follow boardroom skill.md steps and documented c
- Use cases
- orchestration
What c-level-advisor says it does
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 multi
**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.
npx skills add https://github.com/alirezarezvani/claude-skills --skill c-level-advisorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.8k |
|---|---|
| repo stars | ★ 23.5k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 17, 2026 |
| Repository | alirezarezvani/claude-skills ↗ |
When should an agent use boardroom and what problem does it solve?
/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
Who is it for?
Developers invoking boardroom as documented in the skill source.
Skip if: Skip when requirements fall outside boardroom documented scope.
When should I use this skill?
/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
What you get
Outputs aligned with the boardroom SKILL.md workflow and stated deliverables.
- Company-context profile
- Structured C-suite recommendations
- Board-meeting decision summary
By the numbers
- Bundles 28 skills, 25 scripts, and 52 references
- Covers 10 C-level advisory roles
- Published as version 2.0.0 (updated 2026-03-05)
Files
/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 hereThe 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-advocateagent runs/em:challengeon 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:decidefor 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
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
/cs:decide— log approved memo/cs:cross-eval— high-stakes second opinion/cs:freeze— cooldown lock
Related
- Agent: `cs-chief-of-staff`
- Skills: `board-meeting`, `executive-mentor`
---
Version: 1.0.0
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Pick C-Level Advisor when a decision needs multi-disciplinary executive framing; use a single-domain PM or security skill for narrower scope.
FAQ
What is boardroom?
/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
When should I use boardroom?
/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
Is boardroom safe to install?
Review the Security Audits panel on this page before production use.