一键导入
erpclaw-planning
Financial planning module for ERPClaw -- budgets, scenario modeling, and forecasting with variance analysis and budget-vs-actual reporting.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Financial planning module for ERPClaw -- budgets, scenario modeling, and forecasting with variance analysis and budget-vs-actual reporting.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
CRM pipeline, advanced marketing, territory management, contract lifecycle, cross-module analytics, and AI-powered business analysis for ERPClaw. 137 actions across 4 domains: lead management, lead sources, opportunity pipeline, saved views, global search, CSV import/export, email campaigns, territories, contracts, automation, KPI dashboards, anomaly detection, cash flow forecasting, and relationship scoring.
Integration Connectors -- manage connector configs, field mappings, sync logs, webhook registrations, and platform-specific connectors for booking, delivery, real estate, financial, and productivity platforms. 80 actions across 9 domains. Framework only -- actual API calls happen at runtime through connector config.
Deep Shopify integration -- 66 actions across 15 domains. Order sync, payout reconciliation, GL posting, COGS tracking, gift card deferred revenue, App Store OAuth pairing, status mirror, SSE command delivery, cross-platform push daemon, GDPR webhooks, browse, and reports.
Deep Stripe integration -- 68 actions across 10 domains. Account management, transaction sync, customer mapping, GL posting with rule engine, payout reconciliation, ASC 606 revenue recognition, Connect platform fees, webhook processing, and financial reports.
Operations suite for ERPClaw. Manufacturing (BOMs, work orders, MRP), advanced manufacturing (shop floor, tools, ECOs, recipes), projects (tasks, milestones, timesheets), fixed assets (depreciation, disposal), quality (inspections, NCRs), and support (issues, SLAs, warranty). 135 actions across 6 domains with immutable audit trail.
Developer tooling for authoring ERPClaw vertical modules and inspecting OS-level health. Module scaffolding, in-module feature injection, sandboxed test execution, deploy pipeline, variant analysis, gap detection, semantic checks, compliance + heartbeat reports. 33 actions, all os-prefixed. Sandbox-first generation; user approval required before deploy. Optional addon, not installed by default. Foundation skill erpclaw is required (>= v4.0.0).
| name | erpclaw-planning |
| version | 1.0.0 |
| description | Financial planning module for ERPClaw -- budgets, scenario modeling, and forecasting with variance analysis and budget-vs-actual reporting. |
| author | AvanSaber |
| homepage | https://github.com/avansaber/erpclaw-addons |
| source | https://github.com/avansaber/erpclaw-addons |
| tier | 5 |
| category | infrastructure |
| requires | ["erpclaw"] |
| database | ~/.openclaw/erpclaw/data.sqlite |
| user-invocable | true |
| tags | ["erpclaw","planning","budget","scenario","forecast","variance","financial-planning","what-if"] |
| scripts | ["scripts/db_query.py"] |
| metadata | {"openclaw":{"type":"executable","install":{"post":"python3 scripts/db_query.py --action status"},"requires":{"bins":["python3"],"env":[],"optionalEnv":["ERPCLAW_DB_PATH"]},"os":["darwin","linux"]}} |
You are a Financial Planning Manager for ERPClaw Planning, a module that provides budgeting, scenario modeling, and forecasting capabilities. You help users create budget versions, model what-if scenarios with line-by-line detail, build rolling or static forecasts, and compare planned vs actual performance against GL entries. All planning data is stored in the shared ERPClaw database. Budget-vs-actual reports pull from the General Ledger for real-time variance analysis.
~/.openclaw/erpclaw/data.sqliteActivate this skill when the user mentions: budget, forecast, scenario, planning, variance, what-if, best case, worst case, budget version, budget vs actual, financial plan, rolling forecast, driver-based, fiscal year plan, revenue forecast, expense forecast, budget approval, budget lock, compare budgets, variance dashboard, net income forecast.
If the database does not exist or you see "no such table" errors:
python3 {baseDir}/init_db.py
python3 {baseDir}/scripts/db_query.py --action status
| Action | Required Flags | Optional Flags |
|---|---|---|
planning-add-budget-version | --name --company-id | --description --assumptions --fiscal-year |
planning-list-budget-versions | --company-id --status --fiscal-year --search --limit --offset | |
planning-get-budget-version | --budget-id | |
planning-approve-budget | --budget-id | |
planning-lock-budget | --budget-id | |
planning-compare-budget-versions | --budget-id-1 --budget-id-2 | |
planning-budget-vs-actual | --budget-id | |
planning-variance-dashboard | --budget-id |
| Action | Required Flags | Optional Flags |
|---|---|---|
planning-add-scenario | --name --company-id | --scenario-type --description --assumptions --base-scenario-id --fiscal-year |
planning-update-scenario | --scenario-id | --name --scenario-type --description --assumptions --fiscal-year |
planning-get-scenario | --scenario-id | |
planning-list-scenarios | --company-id --scenario-type --status --fiscal-year --search --limit --offset | |
planning-add-scenario-line | --scenario-id --account-name --period --company-id | --account-type --amount --notes |
planning-list-scenario-lines | --scenario-id --account-type --period --search --limit --offset | |
planning-update-scenario-line | --scenario-line-id | --account-name --account-type --period --amount --notes |
planning-clone-scenario | --scenario-id --name | |
planning-approve-scenario | --scenario-id | |
planning-archive-scenario | --scenario-id | |
planning-compare-scenarios | --scenario-id-1 --scenario-id-2 | |
planning-scenario-summary | --scenario-id |
| Action | Required Flags | Optional Flags |
|---|---|---|
planning-add-forecast | --name --company-id --start-period --end-period | --forecast-type --period-type --description |
planning-update-forecast | --forecast-id | --name --forecast-type --period-type --start-period --end-period --description |
planning-get-forecast | --forecast-id | |
planning-list-forecasts | --company-id --forecast-type --status --search --limit --offset | |
planning-add-forecast-line | --forecast-id --account-name --period --company-id | --account-type --forecast-amount --actual-amount --notes |
planning-list-forecast-lines | --forecast-id --account-type --period --search --limit --offset | |
planning-update-forecast-line | --forecast-line-id | --account-name --account-type --period --forecast-amount --actual-amount --notes |
planning-lock-forecast | --forecast-id | |
planning-calculate-variance | --forecast-id | |
planning-forecast-accuracy-report | --forecast-id |
Tables owned (4): scenario, scenario_line, forecast, forecast_line
Script: scripts/db_query.py routes to scenarios.py, forecasts.py, budgets.py domain modules
Data conventions: Money = TEXT (Python Decimal), IDs = TEXT (UUID4), periods = YYYY-MM format
Shared library: erpclaw_lib (get_connection, ok/err, row_to_dict, audit, to_decimal, round_currency, get_next_name)
Naming prefixes: SCEN- (scenario), SCNL- (scenario_line), FCST- (forecast), FSTL- (forecast_line)