thirteen-week-cash-forecast
Skill15 starsChanged 3 months agoMITView on GitHub
Projects weekly cash balance from actual inflows and outflows via a bundled calculator, flags the exact week the balance would breach a stated minimum, and sizes the shortfall, instead of a monthly cash view that's too coarse to catch a short but real liquidity gap. Use whenever the user needs near-term cash visibility, wants a rolling 13-week cash view, or has only a monthly cash forecast that's too coarse to catch a specific week where cash gets genuinely tight.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- adoptai/cpa-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- adoptai/cpa-skills★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- annual-operating-planSkill
- ar-ap-aging-analyzerSkill
- balance-sheet-health-checkSkill
- board-reporting-pack-builderSkill
- capex-roi-evaluatorSkill
- cash-runway-burn-analyzerSkill
- covenant-headroom-monitorSkill
- credit-risk-scoringSkill
- debt-schedule-modelSkill
- driver-based-budget-builderSkill
- fx-exposure-advisorSkill
- kpi-tree-dashboardSkill
- liquidity-stress-testSkill
- margin-decompositionSkill
- month-end-close-acceleratorSkill
- peer-benchmarkingSkill
- recurring-report-builderSkill
- rolling-forecast-builderSkill
- scenario-planning-engineSkill
- three-statement-modelSkill
- variance-bridge-analyzerSkill
- working-capital-optimizerSkill
- zero-based-budget-plannerSkill
The file
Files
Thirteen-Week Cash Forecast
When to use
Use whenever near-term cash visibility matters more than annual or monthly views — a business managing tight liquidity, preparing for a lender conversation, or simply wanting an early warning system for cash rather than finding out about a shortfall after it happens. A monthly cash view can show a comfortable average while hiding a specific week where the balance actually goes uncomfortably low.
What it does
Projects the cash balance week by week from actual and projected inflows and outflows via a bundled calculator (the direct method, tracking real cash movements rather than deriving cash from an accrual P&L), and flags the exact week and dollar amount by which the balance would breach a stated minimum cash threshold, if any week does.
Method
- Build inflows and outflows from real, specific sources for each of the 13 weeks — actual collections expected (tied to the AR aging), actual payments scheduled (tied to AP aging and payroll dates), not a smoothed average of a monthly number divided by 4.3.
- Use the direct method: track actual cash receipts and disbursements, not net income adjusted for non-cash items — the 13-week forecast's entire value is showing real cash timing, which an indirect, accrual-based method obscures.
- State the minimum cash balance the business needs to maintain — whatever operational or covenant-driven floor actually matters, not zero.
- Run the bundled calculator (
scripts/thirteen_week.py) to get the week-by-week balance and an explicit flag for the first week (and every week) the balance would drop below that minimum. - Treat a breach flag as needing a specific action before that week arrives, not just an observation — draw on an available credit line, accelerate a specific receivable, delay a specific payable, or cut a specific planned outflow, named concretely rather than "we'll figure it out."
- Refresh the forecast weekly, rolling the horizon forward, since a 13-week forecast built once and left untouched loses its main value, which is catching a problem with enough lead time to act.
- Compare this week's actuals against last week's forecast for the same week as a standing accuracy check — a forecast that's consistently off in the same direction needs its underlying assumptions revisited, not just this week's numbers.
Inputs
- Starting cash balance
- Weekly inflows and outflows for the 13-week horizon, built from real AR/AP timing and payroll dates
- The minimum cash balance the business needs to maintain
- Config saved as JSON matching the format documented at the top of
scripts/thirteen_week.py
Output format
Week-by-week table of inflows, outflows, net cash movement, ending balance, and headroom versus the minimum; explicit flag on the first breach week if any week's balance drops below the stated minimum, with the shortfall amount.
Example
A monthly cash view shows the business comfortably cash-positive all quarter. The 13-week direct-method forecast reveals that in isolation, week 9 through week 13 show declining headroom as a large payroll and a vendor payment cluster in the same window while a major customer payment lands a week later than usual, though in this run the balance stays above the $200K minimum throughout, ending week 13 with $235,980, still $36K of headroom, a genuinely tight but not breaching result the monthly view alone would never have shown with this level of week-specific detail.
Common pitfalls
- Building the forecast from a smoothed monthly average instead of real weekly inflow and outflow timing, hiding a specific tight week inside a comfortable average.
- Using the indirect, accrual-based method instead of tracking actual cash receipts and disbursements.
- Building the forecast once and not refreshing it weekly, losing the early-warning value that's the entire point of a 13-week view.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

