/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 question |
Route |
| burn, runway, fundraise, dilution, model, LTV, CAC |
cs-cfo-advisor |
| pipeline, win rate, forecast, NRR, churn, ramp |
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:gc-review |
| strategy, vision, board, M&A, raise, exit |
cs-ceo-advisor |
| 2+ signals from different roles |
/cs:boardroom |
| ambiguous |
/cs: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
/cs:brief and trigger /cs:boardroom
- If ambiguous / no signal match: trigger
/cs: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:** /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 "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
1---2name: founder-mode3description: Founder Mode4---56# /cs:founder-mode — The Auto-Router78**Command:** `/cs:founder-mode <question>`910The single command a founder needs to remember. Routes the question to the right C-role automatically, or triggers `/cs:boardroom` if multi-role.1112This 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.1314## Routing Logic1516The router (via `cs-chief-of-staff`) does keyword + intent matching:1718| Signal in question | Route |19|---|---|20| burn, runway, fundraise, dilution, model, LTV, CAC | `cs-cfo-advisor` |21| pipeline, win rate, forecast, NRR, churn, ramp | `cs-cro-advisor` |22| positioning, ICP, message, brand, channel, campaign | `cs-cmo-advisor` |23| roadmap, PMF, JTBD, North Star, RICE, kill | `cs-cpo-advisor` |24| cadence, OKR, scorecard, DRI, operating system, rhythm | `cs-coo-advisor` |25| hiring, comp, ladder, level, attrition, eNPS, equity | `cs-chro-advisor` |26| security, threat, breach, compliance, audit, SOC 2 | `cs-ciso-advisor` |27| architecture, scaling, tech debt, SLO, latency | `cs-cto-advisor` |28| contract, IP, term sheet, regulator, license | `/cs:gc-review` |29| strategy, vision, board, M&A, raise, exit | `cs-ceo-advisor` |30| **2+ signals from different roles** | `/cs:boardroom` |31| **ambiguous** | `/cs:office-hours` first, then route |3233## Workflow34351. Parse the question for role signals362. If exactly one role: invoke that cs-* agent directly373. If 2+ roles: build a brief via `/cs:brief` and trigger `/cs:boardroom`384. If ambiguous / no signal match: trigger `/cs:office-hours` to force the founder to sharpen395. Log the routing decision (raw layer) via `decision-logger`4041## Output4243The router emits one of three responses:4445### Single-role route46```47**Routing:** cs-cfo-advisor48**Why:** Question hits burn rate and unit economics.49**Next:** Invoking cs-cfo-advisor with company-context loaded.5051[Advisor's response follows]52```5354### Multi-role route55```56**Routing:** /cs:boardroom57**Why:** Question touches CFO + CMO + CPO (pricing change has finance, positioning, and product implications).58**Next:** Building brief via /cs:brief, then running boardroom.5960Brief saved: ~/.claude/briefs/2026-05-12-pricing-v3.md61Run: /cs:boardroom ~/.claude/briefs/2026-05-12-pricing-v3.md62```6364### Ambiguous → office hours65```66**Routing:** /cs:office-hours67**Why:** Question is too broad ("should we grow faster?"). Need framing before any advisor can help.68**Next:** Six-question intake.6970[Office hours questions follow]71```7273## Why This Is the Killer Command7475gstack 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.7677## Examples7879```80/cs:founder-mode "should we raise a Series B now or wait 6 months?"81 → boardroom (CFO + CEO + CRO touched)8283/cs:founder-mode "the win rate dropped 20% this month"84 → cs-cro-advisor8586/cs:founder-mode "let's hire a VP Marketing"87 → boardroom (CHRO + CMO + CFO touched)8889/cs:founder-mode "should we be growing faster?"90 → /cs:office-hours (too ambiguous)91```9293## Related9495- Agent: [`cs-chief-of-staff`](../../agents/cs-chief-of-staff.md) — does the routing96- Skill: [`chief-of-staff`](../../../skills/chief-of-staff/SKILL.md) — routing logic97- Skill: [`context-engine`](../../../skills/context-engine/SKILL.md) — loads context9899---100101**Version:** 1.0.0
timdevai