Month-end close status: progress, overdue and blocked tasks, and what can start now
One command in the Fund operations pack, available in the CLI, as an MCP tool and as a JavaScript import: fundops close-status.
What it needs, and why
Every input is checked before anything is calculated. tasks and asOf are required; the rest refine the answer.
| Input | Required | The question it asks | Why it matters |
|---|---|---|---|
tasks | yes | What are the close tasks, with owner, due date, status and dependencies? | Progress and readiness come from the task list. |
asOf | yes | What date should status be measured at? | Overdue depends on it. |
Requests it answers
- “where are we on the close”
- “what is overdue for month end”
- “what can we start next”
An agent with this pack loaded picks the command from phrasing like that, asks for whatever input is missing, and reports the figures with the method that produced them.
Run it
node bin/wealth-skills.js fundops close-status --as-of 2026-09-07 --tasks '[{"id":"bank","name":"Bank reconciliations","status":"done","due":"2026-09-03"},{"id":"nav","name":"NAV strike","status":"not_started","due":"2026-09-08","dependsOn":["bank"]}]'Limits it inherits from wealth-fund-ops
- Reconciliation matches on account and security exactly as supplied; it does not map identifiers or apply corporate actions.
- NAV tie-out recomputes from the supplied assets and liabilities; it values nothing itself.
- Statement checks confirm the arithmetic and consistency with fund terms, not that the underlying values are right.
- Nothing here posts entries or strikes a NAV. Results go to the administrator or controller.
The full pack, its other 3 commands and what it deliberately leaves alone are on the Fund operations page.