Company Cfo
Monthly CFO workflow for a company or agency, pull raw data from bank + payment...
Install
npx skills add coreyhaines31/makerskills --skill company-cfo -g -a claude-code -y- Repository
- coreyhaines31/makerskills880
- Category
- Writing
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Monthly CFO workflow for a company or agency, pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes, monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse.
/company-cfo, Monthly company CFO workflow
The standing analysis leadership uses to make distribution / cuts / hiring / runway decisions. Primary cadence is monthly (run on the 1st for the closed prior month). Weekly and scenario modes cover the in-between.
Anonymized team-scope sibling to personal-cfo (households). Same discipline (transaction-sum EOM, categorization traps, scenario modeling) applied to company books.
Step 0, Load company config + prior run
Before starting work, read these in order:
- The config doc in
${COMPANY_CFO_ROOT:-$HOME/code/company-cfo}/(CLAUDE.mdorAGENTS.md, whichever exists), your company's specific methodology, data source map, categorization rules, distribution mechanics. This is the source of truth for HOW your company computes things. Don't invent your own methodology. - The most recent report in
${COMPANY_CFO_ROOT}/reports/monthly/, last month's snapshot. Tells you what leadership decided + what was open. - The most recent
*-followup.mdin that folder (if one exists), supplementary decisions, scenario analysis. - Any relevant memory notes in your agent's memory, or
${MAKERSKILLS_MEMORY:-${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/memory}/if it has none, running context: known anomalies, leadership constraints, current churn state. git log --oneline -10in${COMPANY_CFO_ROOT}, what's shipped since the last run.
If the COMPANY_CFO_ROOT dir doesn't exist yet: first-run walkthrough asks the user to mkdir it, seed an AGENTS.md from references/company-config-template.md (symlink CLAUDE.md to it for Claude Code), and set the env var.
