Grocery Budget Audit Skill
Food spending is where budgets go to get lied to — partly because it hides
in four places at once (the big shop, the top-ups, the delivery apps, the
work lunches), and partly because every audit turns moral ("we're so bad").
This one doesn't: it's the [[attention-reset]] method pointed at food money
— chosen spending is protected (the Friday takeaway you love stays), and
only the captured spending is the target: the food thrown away, the
convenience markup on autopilot, the brand tax nobody chose, and the
delivery blur that's really a logistics failure wearing a menu.
What This Skill Produces
- A four-stream ledger: big shops / top-ups / delivery-takeaway / food
out, built from whatever evidence exists (receipts, statements, app
order history — the app history is where the surprise lives)
- The leak report: the four leaks quantified for this household, each
with its real cause (waste is usually a planning gap, not gluttony)
- Per-leak fixes with honest expected ranges — labelled as typical
outcomes to verify against next month, never promised
- A keep-the-joy budget: chosen pleasures named and funded, captured
spending targeted, and the one-month re-audit date
Required Inputs
Ask for (if not already provided):
- The evidence: last month's statements/receipts/app histories — or the
honest-guess version, labelled as such, with the audit flagged as
provisional until real numbers arrive
- Household shape: people, work-lunch patterns, who shops, who cooks
- The chosen pleasures to protect — the spending that's working
- What's been tried and how it died (cash envelopes? meal kits?)
Framework
- Assemble the ledger without commentary. Four streams, one month,
totals per stream. The delivery-app order history is mandatory
evidence if apps are used — memory always undercounts it, and the
gap between guess and history is usually the audit's headline.
- Sort chosen from captured. The planned Friday takeaway: chosen —
protected, budgeted, guilt evicted. The 9pm Tuesday order because
nothing was defrosted: captured — a planning gap, addressable. Same
meal, different category; the distinction does all the work.
- Quantify the four leaks. Waste (what got binned — ask for the
honest recurring victims; multiply out) · convenience markup
(top-up-shop pricing, pre-cut everything — the top-up trip count is
the lever, not the lettuce) · brand autopilot (the categories where
own-brand is identical; typically pantry staples, cleaning, basics) ·
the delivery blur (fees + markups + the order-because-tired pattern —
fix is [[meal-prep-os]]'s Thursday plan, not willpower).
- Fix per leak, sized honestly. Each fix names its mechanism and a
typical range ("top-up trips 4→1/week commonly saves 10-20% of that
stream — verify against your month"). No global "slash your bill 50%"
claims; the re-audit is the referee.
- Set the budget with the joy line in it. Streams budgeted with the
chosen items explicitly inside; one flexible buffer; the rule that
protects the system: overspend gets investigated (which leak?) not
punished. Re-audit in one month against real numbers.
Output Format
## The ledger — [month]
| Stream | Total | Biggest line | Chosen / captured split |
[The guess-vs-history gap, if apps were involved]
## Leak report
| Leak | This household's number | Real cause |
## Fixes (ranges to verify, not promises)
[Per leak: mechanism · typical range · this household's version]
## The budget (joy included)
[Per stream · the protected list · buffer · the investigate-don't-punish
rule · re-audit date]
Quality Checks
Anti-Patterns
Related
[[meal-prep-os]] is the fix for half the leaks; [[attention-reset]] — the
same chosen/captured method, different currency; [[debt-payoff]] when the
found money needs a destination.
1---2name: grocery-budget-audit-23description: "Find where the food money actually goes — a no-shame ledger built from real receipts/statements, the four leak categories (waste, convenience markup, brand autopilot, the takeaway blur), a per-leak fix with realistic savings ranges, and a target budget that survives real life. Use when someone says 'we spend how much on food?!', 'audit my grocery spending', 'cut our food bill', or takeaway guilt is the household argument. Produces the ledger, the leak report, and a keep-the-joy budget."4homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/grocery-budget-audit.html5metadata:6 source: https://skillmd.com/skills/mohitagw15856/grocery-budget-audit-27 openclaw:8 emoji: 🧠9---1011# Grocery Budget Audit Skill1213Food spending is where budgets go to get lied to — partly because it hides14in four places at once (the big shop, the top-ups, the delivery apps, the15work lunches), and partly because every audit turns moral ("we're so bad").16This one doesn't: it's the [[attention-reset]] method pointed at food money17— chosen spending is protected (the Friday takeaway you love stays), and18only the *captured* spending is the target: the food thrown away, the19convenience markup on autopilot, the brand tax nobody chose, and the20delivery blur that's really a logistics failure wearing a menu.2122## What This Skill Produces2324- A **four-stream ledger**: big shops / top-ups / delivery-takeaway / food25 out, built from whatever evidence exists (receipts, statements, app26 order history — the app history is where the surprise lives)27- The **leak report**: the four leaks quantified for this household, each28 with its real cause (waste is usually a planning gap, not gluttony)29- **Per-leak fixes** with honest expected ranges — labelled as typical30 outcomes to verify against next month, never promised31- A **keep-the-joy budget**: chosen pleasures named and funded, captured32 spending targeted, and the one-month re-audit date3334## Required Inputs3536Ask for (if not already provided):37- The evidence: last month's statements/receipts/app histories — or the38 honest-guess version, labelled as such, with the audit flagged as39 provisional until real numbers arrive40- Household shape: people, work-lunch patterns, who shops, who cooks41- The chosen pleasures to protect — the spending that's working42- What's been tried and how it died (cash envelopes? meal kits?)4344## Framework45461. **Assemble the ledger without commentary.** Four streams, one month,47 totals per stream. The delivery-app order history is mandatory48 evidence if apps are used — memory *always* undercounts it, and the49 gap between guess and history is usually the audit's headline.502. **Sort chosen from captured.** The planned Friday takeaway: chosen —51 protected, budgeted, guilt evicted. The 9pm Tuesday order because52 nothing was defrosted: captured — a planning gap, addressable. Same53 meal, different category; the distinction does all the work.543. **Quantify the four leaks.** Waste (what got binned — ask for the55 honest recurring victims; multiply out) · convenience markup56 (top-up-shop pricing, pre-cut everything — the top-up *trip count* is57 the lever, not the lettuce) · brand autopilot (the categories where58 own-brand is identical; typically pantry staples, cleaning, basics) ·59 the delivery blur (fees + markups + the order-because-tired pattern —60 fix is [[meal-prep-os]]'s Thursday plan, not willpower).614. **Fix per leak, sized honestly.** Each fix names its mechanism and a62 typical range ("top-up trips 4→1/week commonly saves 10-20% of that63 stream — verify against your month"). No global "slash your bill 50%"64 claims; the re-audit is the referee.655. **Set the budget with the joy line in it.** Streams budgeted with the66 chosen items explicitly inside; one flexible buffer; the rule that67 protects the system: overspend gets *investigated* (which leak?) not68 punished. Re-audit in one month against real numbers.6970## Output Format7172```73## The ledger — [month]74| Stream | Total | Biggest line | Chosen / captured split |75[The guess-vs-history gap, if apps were involved]7677## Leak report78| Leak | This household's number | Real cause |7980## Fixes (ranges to verify, not promises)81[Per leak: mechanism · typical range · this household's version]8283## The budget (joy included)84[Per stream · the protected list · buffer · the investigate-don't-punish85rule · re-audit date]86```8788## Quality Checks8990- [ ] All four streams present; delivery history requested by name when91 apps are in play92- [ ] Chosen spending is explicitly protected and appears IN the budget93- [ ] Every savings number is a labelled range-to-verify, never a promise94- [ ] Waste analysis names actual recurring victims from the inputs, not95 hypothetical lettuce96- [ ] The tone check: zero shame anywhere — data, causes, mechanisms,97 re-audit9899## Anti-Patterns100101- [ ] Do not moralize any line of the ledger — the audit that shames is102 the audit that gets abandoned103- [ ] Do not target the chosen pleasures — cutting the loved takeaway is104 how the whole budget loses its constituency105- [ ] Do not recommend extreme-couponing/13-store optimization — time is106 a cost; the fixes here are structural, not heroic107- [ ] Do not assert current prices or "average household" comparisons as108 fact — this household's month is the only benchmark109- [ ] Do not skip the re-audit date; unverified fixes become folklore110111## Related112113[[meal-prep-os]] is the fix for half the leaks; [[attention-reset]] — the114same chosen/captured method, different currency; [[debt-payoff]] when the115found money needs a destination.