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.
Before & after
Same prompt, same agent — the only difference is the skill.
Those are two major issues that need attention, but they require different expertise. Runway pressure is primarily a financial and operational question - it's about cash flow, burn rate, and prioritization. Retention drop is a product and customer success question - understanding why customers are leaving, what changed, and how to improve. Both are serious but need different solutions. I could help you think through either one separately, but ideally you'd want to get your CFO involved in the runway discussion and your product or customer success lead involved in the retention issue. What would be most urgent to tackle first?
ROUTING ANALYSIS: COMPOUND CRISIS RUNWAY PATH → CFO ADVISOR PRIORITY: IMMEDIATE (week 1) Key questions for financial advisor: 1. Current runway in months (burn rate vs. bank balance) 2. Committed spend (payroll, contracts, obligations) 3. Revenue ramp timeline if retention improves 4. Cost-cutting options if no immediate revenue 5. Fundraising timeline (if pursuing capital) Recommended first action: Monthly cash-flow projection updated daily RETENTION PATH → CCO/PRODUCT ADVISOR PRIORITY: PARALLEL (days 2-3) Key questions for retention advisor: 1. Churn rate by cohort (when did retention drop?) 2. Exit reasons (feature gap, pricing, support, competitor?) 3. Affected customer segment (small/large, new/long-term?) 4. Win-back viability (can churned customers return?) 5. Quick retention lever (discount, feature, support boost?) Recommended first action: Customer exit interviews (top 5 churned accounts) CRISIS CASCADE DYNAMICS • Tight runway limits product investment (retention tool) • Retention drop reduces future revenue (worsens runway math) • This creates a feedback loop SYNCHRONIZATION POINT By day 4: Combine financial constraints + retention data into single scenario: • Scenario A: Cost cuts + retention recovery timeline • Scenario B: Fundraising + retention investment timeline • Choose path based on probability-weighted outcomes
About this skill
name: founder-mode description: Use when /cs:founder-mode <question> — Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics.
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.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the founder-mode skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Founder Mode; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: founder-mode
description: Use this skill when a founder asks a strategic question without knowing which advisor role or command fits, so it can be routed to the right C-role advisor or a multi-role boardroom session.
version: 1.0.0
category: Business & Ops / Executive Advisory
author: AgentVolt
license: proprietary
tags:
- business-ops
- executive-advisory
---
# Founder Mode
The single entry point for founder questions: reads the question, decides which C-role advisor owns it, and routes there — or to a multi-role session when it cuts across functions.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Gc Review
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
Boardroom
/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis.
Context Engine
Loads and manages company context for all C-suite advisor skills.