Send a founder’s strategic question to the appropriate executive advisor by matching its wording and intent. Questions spanning several roles go to a boardroom discussion, while unclear questions receive an intake to clarify the issue.
/c-level-agents:founder-mode [question] — Auto-routes any founder question to the right C-role advisor or to /c-level-agents:boardroom for multi-role topics. The single-command entry point. Use when a founder asks any strategic question without knowing which advisor or command fits — e.g. 'runway pressure' routes to the CFO, 'gross retention dropped' routes to the CCO.
Review the instructions the agent will receive before you install.
Command: /c-level-agents:founder-mode <question>
The single command a founder needs to remember. Routes the question to the right C-role automatically, or triggers /c-level-agents:boardroom if multi-role.
This is the killer command — the answer to "I don't know which slash command to use." Type the question; the system figures out the room.
The router (via cs-chief-of-staff) does keyword + intent matching:
| Signal in question | Route |
|---|---|
| burn, runway, fundraise, dilution, model, LTV, CAC | cs-cfo-advisor |
| pipeline, win rate, forecast, quota, ramp, sales motion | cs-cro-advisor |
| positioning, ICP, message, brand, channel, campaign | cs-cmo-advisor |
| roadmap, PMF, JTBD, North Star, RICE, kill | cs-cpo-advisor |
| cadence, OKR, scorecard, DRI, operating system, rhythm | cs-coo-advisor |
| hiring, comp, ladder, level, attrition, eNPS, equity | cs-chro-advisor |
| security, threat, breach, compliance, audit, SOC 2 | cs-ciso-advisor |
| architecture, scaling, tech debt, SLO, latency | cs-cto-advisor |
| contract, IP, term sheet, regulator, license | cs-general-counsel-advisor |
| retention, GRR, NRR, churn, customer success, CSM, time-to-value, renewals | cs-cco-advisor |
| training data, data rights, consent, data asset, warehouse, lakehouse, data mesh | cs-cdo-advisor |
| model selection, eval, hallucination, AI risk, EU AI Act, fine-tune, build vs buy AI | cs-caio-advisor |
| DORA, cycle time, deploy frequency, eng hiring funnel, team topology, delivery throughput | cs-vpe-advisor |
| strategy, vision, board, M&A, raise, exit | cs-ceo-advisor |
| 2+ signals from different roles | /c-level-agents:boardroom |
| ambiguous | /c-level-agents:office-hours first, then route |
/c-level-agents:brief and trigger /c-level-agents:boardroom/c-level-agents:office-hours to force the founder to sharpendecision-loggerThe router emits one of three responses:
**Routing:** cs-cfo-advisor
**Why:** Question hits burn rate and unit economics.
**Next:** Invoking cs-cfo-advisor with company-context loaded.
[Advisor's response follows]
**Routing:** /c-level-agents:boardroom
**Why:** Question touches CFO + CMO + CPO (pricing change has finance, positioning, and product implications).
**Next:** Building brief via /c-level-agents:brief, then running boardroom.
Brief saved: ~/.claude/briefs/2026-05-12-pricing-v3.md
Run: /c-level-agents:boardroom ~/.claude/briefs/2026-05-12-pricing-v3.md
**Routing:** /c-level-agents:office-hours
**Why:** Question is too broad ("should we grow faster?"). Need framing before any advisor can help.
**Next:** Six-question intake.
[Office hours questions follow]
gstack requires the founder to know all 23 slash commands and pick the right one. That's a cognitive tax. /c-level-agents:founder-mode collapses that to one — the system picks. This is also where persistent memory pays off: with company-context.md + decision-logger, the router knows what's already been decided and won't re-litigate.
/c-level-agents:founder-mode "should we raise a Series B now or wait 6 months?"
→ boardroom (CFO + CEO + CRO touched)
/c-level-agents:founder-mode "the win rate dropped 20% this month"
→ cs-cro-advisor
/c-level-agents:founder-mode "gross retention dropped 5 points this quarter"
→ cs-cco-advisor
/c-level-agents:founder-mode "let's hire a VP Marketing"
→ boardroom (CHRO + CMO + CFO touched)
/c-level-agents:founder-mode "should we be growing faster?"
→ /c-level-agents:office-hours (too ambiguous)
cs-chief-of-staff — does the routingchief-of-staff — routing logiccontext-engine — loads contextVersion: 1.0.0
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.
Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.
Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.
Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.
Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.
Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.