alirezarezvani/cfo-review
c-level-advisor/c-level-agents/skills/cfo-review/SKILL.md
/cs:cfo-review <plan> — Numerate-skeptic interrogation of any plan that touches money. Unit economics, runway, dilution, capital allocation.
$ install --global
skillsauthnpx skillsauth add alirezarezvani/claude-skills cfo-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 14, 2026, 3:31 AM169.3s1 file scanned
SKILL.md
- name:
- cfo-review
- description:
- /cs:cfo-review <plan> — Numerate-skeptic interrogation of any plan that touches money. Unit economics, runway, dilution, capital allocation.
/cs:cfo-review — CFO Forcing Questions
Command: /cs:cfo-review <plan>
The numerate skeptic stress-tests anything that touches money. Six questions before any spend or fundraise.
When to Run
- Before approving any spend > 1% of revenue
- Before opening a new hiring requisition
- Before any fundraise conversation
- Before changing pricing or unit economics
- Before signing a multi-year contract
The Six CFO Questions
1. Burn & Runway
What's the burn multiple and how many months of cash remain at base / bull / bear?
- Burn multiple = Net burn ÷ Net new ARR. Above 2x is a problem.
- If bear case < 12 months, you're already in fundraising mode.
2. Unit Economics
What is LTV / CAC per channel, and what's the payback period on the top-2 channels?
- LTV / CAC > 3x is healthy. Payback < 12 months is healthy.
- If either is broken, do not scale that channel.
3. Dilution Path
If this plan requires a raise, what's the dilution at base and bear valuations?
- Founder dilution per round.
- Cumulative dilution to next 2 rounds.
4. Capital Allocation Alternative
If this dollar wasn't spent here, where else could it go and what's the expected return?
- Three alternatives: hiring, product, marketing.
- Make the opportunity cost explicit.
5. Revenue Quality
What's the gross margin, and how does it trend at scale?
- If margin compresses with scale, the model is broken.
- Cost-of-revenue should grow slower than revenue.
6. Bear Case Survival
If revenue is 50% of plan, does the company survive 18 months?
- Default-alive is non-negotiable.
- If not, identify the cut triggers in advance.
Workflow
- Run the numbers:
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 - Answer all six questions with numbers, not adjectives.
- Apply the verdict:
- 🟢 GREEN — fund it
- 🟡 YELLOW — fund with cut triggers
- 🔴 RED — kill or revise
Output Format
# 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]
Routing
/cs:decide— log the verdict/cs:execute— build 90-day plan if GREEN/cs:boardroom— escalate if multi-role implications
Related
- Agent:
cs-cfo-advisor - Skill:
cfo-advisor
Version: 1.0.0
Related Skills
alirezarezvani/code-reviewer
tools
VerifiedTrustedCommunity
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C#, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter. Analyzes PRs for complexity and risk, checks code quality for SOLID violations and code smells, generates review reports. Use when reviewing pull requests, analyzing code quality, identifying issues, generating review checklists.
16,546SKILL.mdUpdated May 10, 2026
alirezarezvani/research-ops-skills
tools
VerifiedTrustedCommunity
Use when planning, funding, scoping, or synthesizing enterprise research across workstreams — clinical study design, R&D program finance, market sizing/surveys, or product/user research. Triggers on "design this clinical study", "what sample size", "R&D budget", "burn rate", "capitalize or expense", "TAM SAM SOM", "market sizing", "survey design", "segment the market", "plan user interviews", "usability test", "synthesize research insights". Forks context to route to one of four Research-Operations sub-skills (clinical-research, research-finance, market-research, product-research) and returns a digest. Distinct from ra-qm-team (regulatory submission), finance (corporate close/valuation), research/grants (funding discovery), product-team (persona/journey/live experiments), and marketing-skill (campaign analytics).
16,359SKILL.mdUpdated May 28, 2026
alirezarezvani/research-finance
development
VerifiedTrustedCommunity
Use when managing the money for an internal R&D program or portfolio — building a multi-period program budget with the F&A (indirect) split, tracking burn rate and runway against value-inflection milestones, or routing R&D cost items to a capitalize-vs-expense determination. Every budget output surfaces its assumptions block; capitalize-vs-expense is decision-support only and routes to a named finance owner — it never books an entry or decides accounting treatment. Distinct from finance/financial-analysis (corporate DCF, close, valuation) and research/grants (funding discovery — this manages money already won).
16,359SKILL.mdUpdated May 28, 2026
alirezarezvani/product-research
development
VerifiedTrustedCommunity
Use when planning and synthesizing product/user research as a method-and-repository discipline — selecting the right method for the goal (generative interviews vs usability test vs concept test vs validation), computing method-based saturation/sample size with an explicit confidence level, or synthesizing coded observations into insights while flagging single-source anecdotes. Never fabricates user insight; an insight requires recurrence across independent participants. Distinct from product-team/ux-researcher-designer (persona/journey artifacts), product-discovery (discovery-sprint planning), and experiment-designer (live A/B) — this is the research-ops method + insight-repository layer.
16,359SKILL.mdUpdated May 28, 2026