Run an ACF completeness audit

Before a directory, a catalog, or a team page goes live, the quiet worry is the half-finished entry: the profile with no photo, the product with a blank spec, the listing missing its one required line. ACF will happily let a post save with empty fields, so nothing warns you until a visitor finds the hole.

This is the check you run first. It reads the fields you care about across the posts you point it at and hands back a gap report, and it cannot change a thing.

I want to know which of my [staff] profiles are missing required custom fields
before we publish the new directory. Read only, change nothing.

First show me the ACF field groups so we can agree on which fields count as
required: [role, headshot, and bio]. Then, for the post IDs I paste below, read
the ACF values on each one and build me a table with a row per post and a column
per required field, marking each cell filled or empty. Put the posts with the
most gaps at the top, and give me a one-line count of how many are complete
versus how many still need work.

Why this is safe to run

Both abilities behind this prompt are reads. Listing the field groups returns their structure only, never any stored value, and reading a post’s ACF values cannot write, so the worst case is that a field you left switched off quietly returns nothing. There is no write ability in the recipe at all, which is why it is safe to run again after every round of fixes to confirm the gaps are closing.

Already connected? Skip the paste. Ask your agent for the “ACF completeness audit” recipe, or just ask which posts are missing their custom fields, and it runs the same reads on your own install.