← ClaudeAtlas

account-forecastlisted

Per-account forecast of upcoming transactions with running balance and insufficient-funds flags. Shows what comes off which account and when. Run before scheduling payments, or any time you need to check whether a specific account can cover what's coming.
markbaindesign/bain-studio · ★ 0 · AI & Automation · score 61
Install: claude install-skill markbaindesign/bain-studio
# Account Forecast A ledger-level view, not a business one: for each bank account, what's about to come off it, in what order, and whether the balance goes negative before it recovers. ## Steps ### 0. Load business context Read `/media/data/Dropbox/Work/Admin/Financial/Accounting/aletheia-codex.md` before anything else. It's the authoritative record of account topology and which obligations draw from which account. ### 1. Read the financial snapshot Read `/media/data/Dropbox/Work/Admin/Financial/Accounting/accounts.json`. If more than 24 hours old, run `python3 studio/collectors/gnucash_collector.py` to refresh. Key fields: - `bank_balances` — current balance per account - `upcoming_all` — every predicted transaction, each with `date`, `label`, `amount`, `type` (`fixed`, `tax`, `draw`, `income`, ...), and `account` ### 2. Split unattributed transactions Some recurring items in `upcoming_all` have `account: "Unknown"` — the source data doesn't yet say which account they draw from. Pull these into a separate "unassigned" list and call them out explicitly. Don't guess which account they belong to and don't fold them into any account's running balance — a wrong guess is worse than an honest gap. ### 3. Group and project, per account For each named account (not "Unknown"): - Start from its current balance (`bank_balances`). - Sort its transactions from `upcoming_all` by date, ascending. - Walk forward: income/inflow types add to the running balance, everything else subt