Know what every dish costs before you plate it: 10 AI skills for recipe costing

recipe-version-control-and-allergen-redeclaration

track every recipe change and re-declare allergens the moment it changes

How the two work together

Claude thinks it through. Paste the Claude prompt into Claude Code, or drop the folder into your skills folder. Claude does the judgement: what to look for, what is worth doing, what is right.

Codex gets it done. At the hand-off point Claude runs Codex on your machine with one command and passes it the Codex prompt. Codex does the mechanical part and hands the result back. Claude checks it before you see it.

No API key to set up: Claude calls the Codex you already have installed. If Codex is not installed, Claude does that half itself and tells you.

Prompt for Claude

---
name: recipe-version-control-and-allergen-redeclaration
description: Keeps a dated version history of every recipe, and the moment an ingredient is added, removed or swapped, checks whether it touches one of the 14 mandated allergens and forces a re-declaration before the dish goes out under its old description. It treats "we changed the sauce" as a compliance event, not a kitchen note. Use every time a recipe changes, especially a PPDS-labelled product.
---

# Every recipe change, dated, and the allergen check it triggers

Give this a recipe's previous and new version. Get back exactly what changed, whether any of the 14 mandated allergens moved because of it, and what has to happen to the menu, notice or label before the new version is served.

## What it does

1. **Diff the two versions line by line**, added, removed, or quantity changed, dated. A changelog with no date is a memory someone will eventually get wrong.
2. **Check every added or removed ingredient against the 14 mandated allergens**: celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, peanuts, sesame, soybeans, sulphur dioxide and sulphites (over ten parts per million), and tree nuts, "including additives, processing aids and any other substances... in the final product."
3. **Where an allergen changed, flag re-declaration everywhere it's stated**: the menu, any written notice, the staff script, and any printed PPDS label.
4. **Apply the PPDS rule where it bites hardest.** Since Natasha's Law, PPDS food "will be required to label it with the name of the food and a full ingredients list", allergens "emphasised within this list." A changed recipe makes every unsold unit under the old label wrong the moment it's used.
5. **Hold the old version live until the new one is fully updated everywhere**: menu, notice, script and any printed label.

## Then it checks

1. Every ingredient added or removed between versions is listed, dated.
2. Each was checked against the full 14-allergen list, not a shortened one.
3. Any allergen whose presence changed has a re-declaration task for every place it's stated.
4. Any PPDS-labelled product with a changed recipe has label reprinting flagged as blocking.
5. No recipe is "live" on the new version while any re-declaration task is still open.

Any check fails: redo once. Failed twice: say what is wrong and stop.

## Rules

- Public information only. Never invent a fact, number or quote, or an allergen presence not in the supplied ingredient data.
- Anything sent in someone's name says whose name it is.
- Never mark a version "live" while a required re-declaration is still outstanding.
- Never treat a quantity-only change as requiring re-declaration unless it crosses the ten parts per million sulphite threshold.
- Working document for the owner to check against their own recipes and current FSA guidance, and a food safety adviser before relying on it with customers. Not food safety advice.

## Built from
- Food Standards Agency, "PPDS allergen labelling changes for restaurants, cafes and pubs", https://www.gov.uk/government/publications/prepacked-for-direct-sale-ppds-allergen-labelling-changes-for-restaurants-cafes-and-pubs/prepacked-for-direct-sale-ppds-allergen-labelling-changes-for-restaurants-cafes-and-pubs, read 4 November 2026: confirms the 1 October 2021 Natasha's Law PPDS label requirement, behind steps 3 and 4.
- Food Standards Agency, "Allergen guidance for food businesses", https://www.gov.uk/government/publications/allergen-guidance-for-food-businesses/allergen-guidance-for-food-businesses, published 2 April 2020, updated 17 July 2026, read 4 November 2026: the 14-allergen list and additives scope, behind step 2.

Prompt for Codex

# recipe-version-control-and-allergen-redeclaration

## You are given
A recipe's previous and new version, each a full ingredient list with quantities, and the effective date of the new version. Whether the dish is sold PPDS, non-prepacked, or both. The current menu wording, allergen notice wording, and staff script, where they exist. Whether any PPDS label stock for the old version is unsold.

## Produce
Write into a `./recipe-version-output/` folder:

1. `version-diff.csv`: `dish_name`, `change_date`, `ingredient_name`, `change_type` (`added`, `removed`, `quantity_changed`, `unchanged`), `old_quantity`, `new_quantity`.
2. `allergen-impact.csv`: `dish_name`, `ingredient_name`, `change_type`, `allergen_affected` (one of the 14 or `none`), `presence_before`, `presence_after` (`present`/`absent`), `redeclaration_required` (`yes` whenever before and after differ).
3. `redeclaration-tasks.csv`: `dish_name`, `location_to_update` (`menu or chalkboard`, `written allergen notice`, `staff script`, `PPDS label`), `current_wording_verbatim`, `required_change`, `status` (`open`/`done`, only `done` with a dated confirmation supplied).
4. `ppds-stock-flag.csv`: `dish_name`, `old_version_ppds_stock_unsold`, `action` (`withdraw and relabel` when stock is unsold and redeclaration is required, else `none required`).
5. `gaps.md` - numbered list of: every `redeclaration_required: yes` row; every `status: open` task; every `withdraw and relabel` row; any dish live on the new version with tasks still open.

## Rules
- Codex diffs, checks against the 14-allergen list, and tracks tasks to closure. It never marks a task `done` without a dated confirmation, and never infers allergen presence from an ingredient's name alone.
- A recipe version is never recorded as live while any of its own tasks are `open`.
- Quantity-only changes are not allergen-affecting unless sulphite content crosses ten parts per million, calculated explicitly, not assumed.
- Unsold PPDS stock is always flagged for action when allergen content has changed; never left as background fact alone.
- British English, GBP, DD Month YYYY dates. No em dashes.
- Every file ends with: this is a working document prepared for the owner to check against their own recipes and current Food Standards Agency guidance, and for a food safety adviser to check before it is relied on with customers. It is not food safety advice.

## Return
The absolute path and row count of each file. Every ingredient change, dated and typed. Every allergen affected, before and after. Every open task, by dish. Any dish flagged for PPDS withdrawal. Any dish found live with tasks still open, reported as an error. The `gaps.md` item count.

Built from the best public work on this

Sources for recipe-version-control-and-allergen-redeclaration

Everything below was opened and read on 4 November 2026. Nothing is cited that could not be loaded.

1. Food Standards Agency, "Prepacked for Direct Sale (PPDS) allergen labelling changes for restaurants, cafes and pubs"

https://www.gov.uk/government/publications/prepacked-for-direct-sale-ppds-allergen-labelling-changes-for-restaurants-cafes-and-pubs/prepacked-for-direct-sale-ppds-allergen-labelling-changes-for-restaurants-cafes-and-pubs, read 4 November 2026.

States plainly: "From 1 October 2021 the requirements for labelling prepacked for direct sale (PPDS) food changed across the UK", under what the page also calls Natasha's Law, applying "to any food business that produces PPDS food." It defines PPDS as "food that is packaged at the same place it is offered or sold to consumers", ready for presentation before it is ordered or selected, and gives sector examples including "prepacked paninis or boxes of pizza which can be reheated at the consumer's request", "prepacked sandwiches or salad boxes" and "pies in packaging". The label requirement: any business producing PPDS food "will be required to label it with the name of the food and a full ingredients list", and "Allergenic ingredients must be emphasised within this list", for example through "bold type, capital letters, contrasting colours or underlined text."

This source is the entire reason step 4 treats a recipe change on a PPDS product as urgent in a way a plain menu item is not: the label is a physical, printed object already in circulation, and a recipe change that alters the ingredients list makes every unsold unit under the old label incorrect the moment the new recipe is first used.

Where the skill departs: the Food Information (Amendment) (England) Regulations 2019 (SI 2019/1218) is the underlying legislation the page summarises; this pack confirmed that Statutory Instrument's existence and structure directly on legislation.gov.uk but could not retrieve its full regulation text at the time of writing, so the skill relies on the FSA's own plain-English page for the substantive requirement rather than quoting the Regulations themselves.

2. Food Standards Agency, "Allergen guidance for food businesses"

https://www.gov.uk/government/publications/allergen-guidance-for-food-businesses/allergen-guidance-for-food-businesses, published 2 April 2020, updated 17 July 2026, read 4 November 2026.

Gives the full 14-allergen list used in step 2: celery, cereals containing gluten (wheat, rye, barley, oats), crustaceans, eggs, fish, lupin, milk, molluscs, mustard, peanuts, sesame, soybeans, sulphur dioxide and sulphites "at a concentration of more than ten parts per million", and tree nuts. It states this "applies to additives, processing aids and any other substances which are present in the final product", which is why an ingredient diff has to check sub-ingredients of any bought-in component, not just headline items.

Where the skill departs: the page is general allergen guidance, covering non-prepacked disclosure methods as well as PPDS labels; this skill uses only the allergen list and the PPDS label-content statement from it, leaving the non-prepacked disclosure methods to the allergen-matrix-builder skill, which owns that part of the job.

Best public prompt we found for this job

The closest public artefact is `tedlin182/gitHubGrub` on GitHub, read from api.github.com on 4 November 2026, which returned a `stargazers_count` of 0 and no description field at all. It is a proposal-stage project for letting people fork and branch recipes the way developers branch code, tracing differences in ingredients and amounts between versions, rather than a finished tool, and it is the weakest-reviewed repository used anywhere in this pack.

What we took: the core idea the name itself points at, that a recipe change is worth treating the way a version-control system treats a code change, as a tracked diff with a before and an after, rather than as an edit that simply overwrites what was there.

What we did not copy, and why: as a concept document rather than working code, it has nothing to copy mechanically, and more importantly it has no notion that some diffs are regulatory events. A version-control system for recipes built by analogy to source code would, by default, treat every change the same way; this skill exists specifically to single out the one kind of change, an allergen moving in or out of a dish, that the law does not let a business shrug off as an ordinary edit, and to tie it to the one artefact, a printed PPDS label, that a software analogy alone would never think to check.

Want this running in your business?

I optimise how businesses run — your sales, your visibility, your social media — and build bespoke software where nothing off the shelf fits. The first conversation is free. Work starts from £150 a day.