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.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- founder-mode
- description
- /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.
03 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 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 | /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:briefand trigger/cs:boardroom - If ambiguous / no signal match: trigger
/cs:office-hoursto 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 "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
- Agent:
cs-chief-of-staff— does the routing - Skill:
chief-of-staff— routing logic - Skill:
context-engine— loads context
Version: 1.0.0
04 同仓库更多 Skills
preamble-gate
Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent/subagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI/triggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log/diff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.
visionary-recommender
暂无简介
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.