C Level Agents
Founder-mode executive team. 8 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff) and 17 /cs:* slash commands for forcing-question office hours, multi-role boardroom delibera...
Founder-mode executive team. 8 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff) and 17 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions.
Install
Quick install
npx skills add https://github.com/alirezarezvani/claude-skills/tree/main/c-level-advisor/c-level-agents/skills/c-level-agentsnpx skills add alirezarezvani/claude-skills --skill c-level-agents --agent claude-codenpx skills add alirezarezvani/claude-skills --skill c-level-agents --agent cursornpx skills add alirezarezvani/claude-skills --skill c-level-agents --agent codexnpx skills add alirezarezvani/claude-skills --skill c-level-agents --agent opencodenpx skills add alirezarezvani/claude-skills --skill c-level-agents --agent github-copilotnpx skills add alirezarezvani/claude-skills --skill c-level-agents --agent windsurfMore install options
Shorthand — useful for multi-skill repos:
npx skills add alirezarezvani/claude-skills --skill c-level-agentsManual — clone the repo and drop the folder into your agent's skills directory:
git clone https://github.com/alirezarezvani/claude-skills.gitcp -r claude-skills/c-level-advisor/c-level-agents/skills/c-level-agents ~/.claude/skills/c-level-agents — Founder-Mode Executive Team
A virtual C-suite delivered through slash commands and persona agents.
Keywords
founder mode, virtual c-suite, executive team, boardroom, office hours, cfo review, cmo review, strategic sprint, decision logging, cross-model consensus, persona agents, chief of staff, forcing questions
What This Plugin Provides
8 cs-* Agents (in agents/)
Each agent wraps an existing c-level skill and adds:
- A distinct cognitive voice (numerate skeptic, narrative-first, etc.)
- Forcing questions specific to the role
- Workflow orchestration tied to skill Python tools
- Output template: Bottom Line → What → Why → How to Act → Your Decision
See ../references/persona-voices.md for voice specs.
17 /cs:* Slash Commands (in skills/)
Forcing-question office hours (8):
/cs:office-hours— YC-style 6-question intake/cs:cfo-review— unit economics, runway, dilution/cs:cmo-review— ICP, CAC payback, positioning/cs:cpo-review— RICE, JTBD, North Star, PMF/cs:cro-review— pipeline coverage, win rate, NRR/cs:cto-review— architecture risk, scaling cliff/cs:ciso-review— threat model, blast radius, compliance/cs:gc-review— contracts, IP, regulatory, term sheets
Strategic sprint pipeline (5):
/cs:brief→/cs:boardroom→/cs:decide→/cs:execute→/cs:post-mortem
Meta + safety (4):
/cs:founder-mode— auto-routes to the right C-role/cs:onboard— founder interview →company-context.md/cs:cross-eval— multi-model consensus/cs:freeze— cooldown lock on a decision
Quick Start
/cs:onboard # populate company context first
/cs:office-hours "should we hire a VP Sales?"
/cs:founder-mode "runway pressure" # auto-routes to CFO
/cs:boardroom briefs/pricing-v3.md # full panel
Architecture
User question
│
├─ Single-role? → cs-{role}-advisor agent
│ ↓
│ /cs:{role}-review command (forcing Qs)
│ ↓
│ Skill tools + references
│ ↓
│ Bottom Line + Memo
│
└─ Multi-role? → /cs:boardroom
↓
6-phase deliberation (Phase 2 isolation)
↓
/cs:decide → decision-logger (two-layer memory)
↓
/cs:execute → 90-day plan
Integration Points
- Existing 28 c-level skills — wrapped, not replaced
- decision-logger — every
/cs:decidewrites here - chief-of-staff — routing layer the agent orchestrates
- board-meeting — protocol the
/cs:boardroomcommand runs - llm-wiki — optional persistent memory bridge (see
../references/llm-wiki-bridge.md) - executive-mentor — adversarial
/em:*commands stack cleanly on top
Design Principles
- Voice is bookended, analysis is neutral.
- Artifacts over chat. Every command produces a Markdown artifact the next command consumes.
- Phase 2 isolation in boardroom. Independent thinking before cross-examination.
- Graceful degradation.
/cs:cross-evalfalls back to Claude-only. - No paid dependencies. All Python tools are stdlib-only.
References
- [persona-voices.md](../../references/persona-voices.md)
- [llm-wiki-bridge.md](../../references/llm-wiki-bridge.md)
- [Parent c-level CLAUDE.md](../../../CLAUDE.md)
- [Existing executive-mentor sibling](../../../executive-mentor/)
---
Version: 1.0.0
Last Updated: 2026-05-12
Status: Production Ready
SKILL.md source
---
name: c-level-agents
description: Founder-mode executive team. 8 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff) and 17 /cs:* slash commands for forcing-question office hours, multi-role boardroom delibera...
---
# c-level-agents — Founder-Mode Executive Team
A virtual C-suite delivered through slash commands and persona agents.
## Keywords
founder mode, virtual c-suite, executive team, boardroom, office hours, cfo review, cmo review, strategic sprint, decision logging, cross-model consensus, persona agents, chief of staff, forcing questions
## What This Plugin Provides
### 8 cs-* Agents (in `agents/`)
Each agent wraps an existing c-level skill and adds:
- A distinct cognitive voice (numerate skeptic, narrative-first, etc.)
- Forcing questions specific to the role
- Workflow orchestration tied to skill Python tools
- Output template: Bottom Line → What → Why → How to Act → Your Decision
See `../references/persona-voices.md` for voice specs.
### 17 /cs:* Slash Commands (in `skills/`)
**Forcing-question office hours (8):**
- `/cs:office-hours` — YC-style 6-question intake
- `/cs:cfo-review` — unit economics, runway, dilution
- `/cs:cmo-review` — ICP, CAC payback, positioning
- `/cs:cpo-review` — RICE, JTBD, North Star, PMF
- `/cs:cro-review` — pipeline coverage, win rate, NRR
- `/cs:cto-review` — architecture risk, scaling cliff
- `/cs:ciso-review` — threat model, blast radius, compliance
- `/cs:gc-review` — contracts, IP, regulatory, term sheets
**Strategic sprint pipeline (5):**
- `/cs:brief` → `/cs:boardroom` → `/cs:decide` → `/cs:execute` → `/cs:post-mortem`
**Meta + safety (4):**
- `/cs:founder-mode` — auto-routes to the right C-role
- `/cs:onboard` — founder interview → `company-context.md`
- `/cs:cross-eval` — multi-model consensus
- `/cs:freeze` — cooldown lock on a decision
## Quick Start
```
/cs:onboard # populate company context first
/cs:office-hours "should we hire a VP Sales?"
/cs:founder-mode "runway pressure" # auto-routes to CFO
/cs:boardroom briefs/pricing-v3.md # full panel
```
## Architecture
```
User question
│
├─ Single-role? → cs-{role}-advisor agent
│ ↓
│ /cs:{role}-review command (forcing Qs)
│ ↓
│ Skill tools + references
│ ↓
│ Bottom Line + Memo
│
└─ Multi-role? → /cs:boardroom
↓
6-phase deliberation (Phase 2 isolation)
↓
/cs:decide → decision-logger (two-layer memory)
↓
/cs:execute → 90-day plan
```
## Integration Points
- **Existing 28 c-level skills** — wrapped, not replaced
- **decision-logger** — every `/cs:decide` writes here
- **chief-of-staff** — routing layer the agent orchestrates
- **board-meeting** — protocol the `/cs:boardroom` command runs
- **llm-wiki** — optional persistent memory bridge (see `../references/llm-wiki-bridge.md`)
- **executive-mentor** — adversarial `/em:*` commands stack cleanly on top
## Design Principles
1. **Voice is bookended, analysis is neutral.**
2. **Artifacts over chat.** Every command produces a Markdown artifact the next command consumes.
3. **Phase 2 isolation in boardroom.** Independent thinking before cross-examination.
4. **Graceful degradation.** `/cs:cross-eval` falls back to Claude-only.
5. **No paid dependencies.** All Python tools are stdlib-only.
## References
- [persona-voices.md](../../references/persona-voices.md)
- [llm-wiki-bridge.md](../../references/llm-wiki-bridge.md)
- [Parent c-level CLAUDE.md](../../../CLAUDE.md)
- [Existing executive-mentor sibling](../../../executive-mentor/)
---
**Version:** 1.0.0
**Last Updated:** 2026-05-12
**Status:** Production Ready
Related skills 6
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
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.
Brief
/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline.
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
Cco Review
/cs:cco-review <plan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring.