← everything it can do · finance

Founder Mode TEXT

Automatically analyzes a founder's strategic question to identify relevant C-suite roles and routes the query to the specific advisor agent or a multi-role boardroom session. It serves as the single entry point for strategic decision-making, handling keyword matching and intent classification to determine the appropriate response workflow.

3 uses this weeksource alirezarezvanilicence MIT

Quality gate: PASS · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift +2.0 points (specificity, structure, method, fit).
won 2/2, lift +2.0, tokens ×20.47

Security scan: clean · 2026-10-24 · 1 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Vi har brug for at skære budgettet med 20%, hvilke områder bør vi se på først?”

“Kundetilfredsheden er faldet markant, hvad gør vi for at vende det?”

“Skal vi lancere produktet i Tyskland nu, eller vente til næste kvartal?”

“My runway is down to 8 months and we need to cut costs, what should I do?”

“The churn rate spiked to 12% last month, why is that happening?”

“We are considering a pivot to enterprise clients, how does that affect our pricing model?”

Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

routingfounderc-suitestrategyauto-dispatchdecision-makingadvisoryorchestration

Not for

Do not use this skill if the user already knows which specific advisor they want to invoke directly (e.g., explicitly calling /c-level-agents:cs-cfo-advisor). It is not for executing specific operational tasks like writing code or generating marketing copy without strategic context. It is not for general Q&A that does not involve C-level strategic decision-making.

Details

When it is the right choice

Use this skill when a founder asks a strategic, operational, or financial question but does not know which specific C-level advisor to consult. It is the correct choice for any high-level business query that requires expert interpretation of role-specific signals (e.g., finance, product, sales). It is also used when the question is ambiguous and needs to be routed to an intake process for clarification.

The full recipe the assistant reads

/c-level-agents:founder-mode — The Auto-Router

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.

Routing Logic

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

Workflow

Parse the question for role signals
If exactly one role: invoke that cs-* agent directly
If 2+ roles: build a brief via /c-level-agents:brief and trigger /c-level-agents:boardroom
If ambiguous / no signal match: trigger /c-level-agents:office-hours to force the founder to sharpen
Log the routing decision (raw layer) via decision-logger

Output

The router emits one of three responses:

Single-role route

**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]

Multi-role route

**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

Ambiguous → office hours

**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]

Why This Is the Killer Command

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.

Examples

/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)

Agent: cs-chief-of-staff — does the routing
Skill: chief-of-staff — routing logic
Skill: context-engine — loads context

Version: 1.0.0

Files in this skill (2)

LICENSE
SKILL.md

Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-agents/skills/founder-mode, licence MIT. The upstream licence file ships inside the skill.