founder-modelisted

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