executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
variance-commentaryWrite flux commentary for every P&L and balance-sheet line over threshold — current vs prior period and vs budget, with the driver explained from underlying activity. Use for the month-end close package and management reporting.
Independent GitHub snapshot · Automated classification · Original documentation governs
Given current-period actuals, prior-period actuals, and budget for the same scope, produce a commentary table.
Flag a line for commentary if either is true:
| Column | Content |
|---|---|
| Line | Account or caption |
| Current / Prior / Budget | The three values |
| Δ vs prior and Δ vs budget | Amount and % |
| Driver | One sentence explaining the movement from underlying activity — not a restatement of the number |
A driver explains why, not what: "Cloud spend up $1.2M on incremental GPU reservations for the May launch" — not "Cloud spend increased $1.2M (18%)."
Look at the activity behind the line (journal-source breakdown, vendor mix, headcount delta, volume × rate) via the internal-gl MCP. If the driver isn't clear from the data, write "driver unclear — flag for controller" rather than inventing one.
The commentary table plus a short narrative (3–5 sentences) summarizing the period's biggest movers.