/cs:cfo-review <plan> — Numerate-skeptic interrogation of any plan that touches money. Unit economics, runway, dilution, capital allocation. Use when a plan commits meaningful spend — e.g. a hiring wave, a fundraise decision, or a new channel budget.
cd ~/.claude/skills
git clone https://github.com/alirezarezvani/claude-skills.git claude-skills mkdir -p ~/.claude/skills/cfo-review
curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.gemini/skills/cfo-review/SKILL.md \
-o ~/.claude/skills/cfo-review/SKILL.md Command: /cs:cfo-review <plan>
The numerate skeptic stress-tests anything that touches money. Six questions before any spend or fundraise.
What’s the burn multiple and how many months of cash remain at base / bull / bear?
What is LTV / CAC per channel, and what’s the payback period on the top-2 channels?
If this plan requires a raise, what’s the dilution at base and bear valuations?
If this dollar wasn’t spent here, where else could it go and what’s the expected return?
What’s the gross margin, and how does it trend at scale?
If revenue is 50% of plan, does the company survive 18 months?
python ../../../skills/cfo-advisor/scripts/burn_rate_calculator.py
python ../../../skills/cfo-advisor/scripts/unit_economics_analyzer.py
python ../../../skills/cfo-advisor/scripts/fundraising_model.py
# CFO Review: <plan>
**Date:** YYYY-MM-DD
**Reviewer:** cs-cfo-advisor
## Numbers
- Burn multiple: X.Xx
- Runway (base/bull/bear): X / X / X months
- LTV/CAC top channel: X.Xx, payback Y months
- Gross margin: X% (trend: Y)
- Dilution this round: X%
- Bear-case survival: PASS / FAIL
## Verdict
🟢 GREEN | 🟡 YELLOW | 🔴 RED
## Conditions (if YELLOW)
- Cut trigger: <metric> < <threshold> → <action>
- Review checkpoint: <date>
## Recommendation
[3 concrete next steps]
/cs:decide — log the verdict/cs:execute — build 90-day plan if GREEN/cs:boardroom — escalate if multi-role implicationscs-cfo-advisorcfo-advisorVersion: 1.0.0
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when creating new skills, editing existing skills, or verifying skills work before deployment