Source profileQuality 90/100

alirezarezvani/claude-skills/c-level-agents/skills/founder-mode/SKILL.md

founder-mode

/cs:founder-mode <question> — Auto-routes any founder question to the right C-role advisor or to /cs: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.

Source repository stars
24,975
Declared platforms
0
Static risk flags
0
Last source update
2026-08-25
Source checked
2026-08-26

Decision brief

What it does: where it fits

Command: /cs:founder-mode

Best for

  • Use when a founder asks any strategic question without knowing which advisor or command fits — e.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/alirezarezvani/claude-skills --skill "c-level-agents/skills/founder-mode"
Safe inspection promptEditorial

Inspect the Agent Skill "founder-mode" from https://github.com/alirezarezvani/claude-skills/blob/f2bac0a8f29b71846cc62d9d580249c2a3246030/c-level-agents/skills/founder-mode/SKILL.md at commit f2bac0a8f29b71846cc62d9d580249c2a3246030. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Parse the question for role signals 2. If exactly one role: invoke that cs- agent directly 3. If 2+ roles: build a brief via /cs:brief and trigger /cs:boardroom 4. If ambiguous / no signal match: trigger /cs:office-hours to force the founder to sharpen 5. Log the routing deci…

    Parse the question for role signalsIf exactly one role: invoke that cs- agent directlyIf 2+ roles: build a brief via /cs:brief and trigger /cs:boardroom
  2. 02

    Routing Logic

    The router (via cs-chief-of-staff) does keyword + intent matching:

    The router (via cs-chief-of-staff) does keyword + intent matching:
  3. 03

    Output

    The router emits one of three responses:

    The router emits one of three responses:
  4. 04

    Single-role route

    Review the “Single-role route” section in the pinned source before continuing.

    Review and apply the “Single-role route” source section.
  5. 05

    Multi-role route

    Review the “Multi-role route” section in the pinned source before continuing.

    Review and apply the “Multi-role route” source section.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score90/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars24,975SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
alirezarezvani/claude-skills
Skill path
c-level-agents/skills/founder-mode/SKILL.md
Commit
f2bac0a8f29b71846cc62d9d580249c2a3246030
License
MIT
Collected
2026-08-26
Default branch
main
View the original SKILL.md

/cs:founder-mode — The Auto-Router

Command: /cs:founder-mode <question>

The single command a founder needs to remember. Routes the question to the right C-role automatically, or triggers /cs: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 questionRoute
burn, runway, fundraise, dilution, model, LTV, CACcs-cfo-advisor
pipeline, win rate, forecast, quota, ramp, sales motioncs-cro-advisor
positioning, ICP, message, brand, channel, campaigncs-cmo-advisor
roadmap, PMF, JTBD, North Star, RICE, killcs-cpo-advisor
cadence, OKR, scorecard, DRI, operating system, rhythmcs-coo-advisor
hiring, comp, ladder, level, attrition, eNPS, equitycs-chro-advisor
security, threat, breach, compliance, audit, SOC 2cs-ciso-advisor
architecture, scaling, tech debt, SLO, latencycs-cto-advisor
contract, IP, term sheet, regulator, licensecs-general-counsel-advisor
retention, GRR, NRR, churn, customer success, CSM, time-to-value, renewalscs-cco-advisor
training data, data rights, consent, data asset, warehouse, lakehouse, data meshcs-cdo-advisor
model selection, eval, hallucination, AI risk, EU AI Act, fine-tune, build vs buy AIcs-caio-advisor
DORA, cycle time, deploy frequency, eng hiring funnel, team topology, delivery throughputcs-vpe-advisor
strategy, vision, board, M&A, raise, exitcs-ceo-advisor
2+ signals from different roles/cs:boardroom
ambiguous/cs:office-hours first, then route

Workflow

  1. Parse the question for role signals
  2. If exactly one role: invoke that cs-* agent directly
  3. If 2+ roles: build a brief via /cs:brief and trigger /cs:boardroom
  4. If ambiguous / no signal match: trigger /cs:office-hours to force the founder to sharpen
  5. 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:** /cs:boardroom
**Why:** Question touches CFO + CMO + CPO (pricing change has finance, positioning, and product implications).
**Next:** Building brief via /cs:brief, then running boardroom.

Brief saved: ~/.claude/briefs/2026-05-12-pricing-v3.md
Run: /cs:boardroom ~/.claude/briefs/2026-05-12-pricing-v3.md

Ambiguous → office hours

**Routing:** /cs: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. /cs: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

/cs:founder-mode "should we raise a Series B now or wait 6 months?"
   → boardroom (CFO + CEO + CRO touched)

/cs:founder-mode "the win rate dropped 20% this month"
   → cs-cro-advisor

/cs:founder-mode "gross retention dropped 5 points this quarter"
   → cs-cco-advisor

/cs:founder-mode "let's hire a VP Marketing"
   → boardroom (CHRO + CMO + CFO touched)

/cs:founder-mode "should we be growing faster?"
   → /cs:office-hours (too ambiguous)

Related


Version: 1.0.0

Frequently asked questions

What to verify before installation and use

What does the founder-mode source document cover?

Command: /cs:founder-mode

How do I install founder-mode?

The source record exposes this install command: npx skills add https://github.com/alirezarezvani/claude-skills --skill "c-level-agents/skills/founder-mode". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 10029,095

garrytan/gbrain

bulk-ingestion

End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

Computed 10024,975

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 10015,246

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

Computed 10014,678

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance