/cs-month-end-close

Slash Command Source

Run the close gates over $ARGUMENTS. Skip any step whose input was not given and say so.

python ${CLAUDE_PLUGIN_ROOT}/skills/month-end-close/scripts/close_calendar_planner.py --plan <close_plan.json>
python ${CLAUDE_PLUGIN_ROOT}/skills/month-end-close/scripts/reconciliation_matcher.py --gl <gl.csv> --source <source.csv> \
  --gl-balance <n> --source-balance <n> --as-of <period end> --preparer <name> --reviewer <name>
python ${CLAUDE_PLUGIN_ROOT}/skills/month-end-close/scripts/flux_analyzer.py --input <tb_compare.csv> --pct <policy> --abs <policy> --reviewer <name>

Ask for any balance, period end, preparer, reviewer or threshold that is missing. Do not assume a materiality threshold.

Report

1. Verdict: BLOCKED if any script exits 4, AT RISK if any exits 2, otherwise READY.
2. Critical path: the chain, its finish workday versus target, and who owns most of it.
3. Blockers: every BLOCKER line verbatim, each with its owner.
4. Reconciliations: proof, unexplained difference and hints, aged items, journal entries needed.
5. Flux: material accounts with failing explanations, and what is missing from each.
6. One change that would remove the most days from the close.