c-level-advisor/c-level-agents/skills/c-level-agents/SKILL.md
Founder-mode executive team. 13 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, GC, CDO, CAIO, CCO, VPE, Chief of Staff) and 21 /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.
npx skillsauth add alirezarezvani/claude-skills c-level-agentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A virtual C-suite delivered through slash commands and persona agents.
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
agents/)Each agent wraps an existing c-level skill and adds:
See ../../references/persona-voices.md for voice specs.
skills/)Forcing-question office hours (12):
/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/cs:cdo-review — training-data rights, data products, data assets/cs:caio-review — model selection, evals, AI risk, AI costs/cs:cco-review — GRR/NRR decomposition, churn root cause, CS coverage/cs:vpe-review — DORA metrics, cycle time, eng hiring funnel, team structureStrategic sprint pipeline (5):
/cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortemMeta + 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/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
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
/cs:decide writes here/cs:boardroom command runs../../references/llm-wiki-bridge.md)/em:* commands stack cleanly on top/cs:cross-eval falls back to Claude-only.Version: 1.0.0 Last Updated: 2026-05-12 Status: Production Ready
development
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.