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 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.
- License 许可
- MIT
- 所属仓库
- HasRahm/jarvis
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- c-level-agents
- license
- MIT
- metadata
- { "agents": "cs-cfo-advisor, cs-cmo-advisor, cs-cro-advisor, cs-cpo-advisor, cs-coo-advisor, cs-chro-advisor, cs-ciso-advisor, cs-chief-of-staff", "author": "Alireza Rezvani", "domain": "executive-orchestration", "updated": 1778544000000, "version": "1.0.0", "category": "c-level", "commands": "cs-office-hours, cs-cfo-review, cs-cmo-review, cs-cpo-review, cs-cro-review, cs-cto-review, cs-ciso-review, cs-gc-review, cs-brief, cs-boardroom, cs-decide, cs-execute, cs-post-mortem, cs-founder-mode, cs-onboard, cs-cross-eval, cs-freeze" }
- 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 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.
03 SKILL.md 正文
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
Version: 1.0.0 Last Updated: 2026-05-12 Status: Production Ready
04 同仓库更多 Skills
youtube-full
Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private/age-restricted videos.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.
workflow-builder
Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.
webinar-marketing
When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.