cfo-review
$
npx mdskill add alirezarezvani/claude-skills/cfo-reviewStress-tests financial plans with CFO-level scrutiny
- Evaluates unit economics, burn rate, and capital allocation risks
- Uses financial metrics and scenario modeling
- Applies six standardized questions to assess financial viability
- Returns prioritized financial risks and alternatives
SKILL.md
.github/skills/cfo-reviewView on GitHub ↗
--- name: "cfo-review" description: "/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." --- # /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 1. **Run the numbers:** ```bash 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 ``` 2. **Answer all six questions** with numbers, not adjectives. 3. **Apply the verdict:** - 🟢 GREEN — fund it - 🟡 YELLOW — fund with cut triggers - 🔴 RED — kill or revise ## Output Format ```markdown # 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`](../../agents/cs-cfo-advisor.md) - Skill: [`cfo-advisor`](../../../skills/cfo-advisor/SKILL.md) --- **Version:** 1.0.0
More from alirezarezvani/claude-skills
- a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
- ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
- ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
- adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
- agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
- agent-workflow-designerDesign production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
- agenthubMulti-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
- agile-product-ownerAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.