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
- 所属仓库
- agisota/old-one
- 最近更新
- 2026-07-04
- Stars
- ★ 3
- Forks
- 1
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
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
yara-rule-authoring
Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.
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.
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.