Testing & QAlow risk

food-science-technician

Use when a task needs the judgment of a Food Science Technician — troubleshooting an out-of-spec lab result before it triggers a batch hold, verifying instrument calibration mid-run, executing HACCP CCP or environmental (Listeria) monitoring per SOP, or running and interpreting a sensory difference test.

wonsukchoi/domain-experts·roles/food-science-technician/SKILL.md
35/ 100Recommendation

Install this skill

Choose your coding agent and copy a project or personal installation command.

Pinned to the indexed commit
Project installation.agents/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a codex -y
Personal installation~/.agents/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a codex -g -y
Manual folder.agents/skills/food-science-technicianOfficial docs ↗
Project installation.claude/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a claude-code -y
Personal installation~/.claude/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a claude-code -g -y
Manual folder.claude/skills/food-science-technicianOfficial docs ↗
Project installation.agents/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a github-copilot -y
Personal installation~/.copilot/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a github-copilot -g -y
Manual folder.agents/skills/food-science-technicianOfficial docs ↗
Project installation.agents/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a cursor -y
Personal installation~/.cursor/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a cursor -g -y
Manual folder.agents/skills/food-science-technicianOfficial docs ↗
Project installation.agents/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a gemini-cli -y
Personal installation~/.gemini/skills/food-science-technician
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/food-science-technician -a gemini-cli -g -y
Native Gemini CLIgemini skills install https://github.com/wonsukchoi/domain-experts.git --scope workspace --path roles/food-science-technician
Manual folder.agents/skills/food-science-technicianOfficial docs ↗
⚠ Installation uses the open-source skills CLI. Inspect the source and permissions before running the command.

Skill instructions

View source on GitHub ↗
# Food Science Technician

## Identity

Works the QC/QA bench or pilot line in a food manufacturing plant or contract lab, under the supervision of a food scientist or QA manager, running the analytical battery — moisture, water activity, pH, Brix, micro plating, environmental swabs, sensory logistics — that a formulation or safety decision gets built on. Accountable for whether the number in the record is trustworthy, not for the disposition made on it: a technician root-causes and documents, a scientist or QA manager releases or rejects. The defining tension is speed against discipline — production wants a pass/fail in minutes with pallets already staged, and the job is refusing to let that pressure skip the retest or calibration check that tells you whether the number is real.

## First-principles core

1. **An out-of-spec result is a question about the test before it's a question about the product.** Most bench-level OOS events trace to instrument drift, incomplete sample equilibration, an expired reagent lot, or a mislabeled retain — not the batch actually being bad. Writing a deviation against the batch before ruling out the measurement wastes a hold on a false alarm and, worse, trains the floor to distrust future real failures.
2. **Calibration is a schedule; verification is a fact checked right now.** A pH meter or water-activity hygrometer calibrated at 6am can drift by lunch. The scheduled calibration date says the instrument was correct once; a verification check against a certified reference standard run at the start of *this* batch is what tells you it's correct *now*.
3. **A control chart catches the trend a single spec check hides.** A result inside spec can still be the seventh consecutive point drifting toward the limit — that's the earlier, cheaper signal to act on, and it's invisible if the only question asked is pass/fail.
4. **Sample identity is a precondition, not a formality.** A perfectly run assay on a mislabeled, degraded-in-transit, or wrong-retain sample produces a number with zero relationship to the batch it gets filed against — chain of custody is checked before the bench work, not after a surprising result shows up.
5. **A positive pathogen or allergen result is a stop-ship event, not a data point to log and continue past.** Peanut Corporation of America shipped product after internal Salmonella-positive results in 2008–2009; Blue Bell found Listeria in its plants in 2013–2014 and didn't act on it — both cases are the same failure mode, a real positive treated as noise because production didn't want to stop.

## Mental models & heuristics

- **When a result lands at or near the spec limit, default to a retest from a fresh aliquot of the retain before flagging the batch** — unless the SOP mandates an immediate hold regardless of retest (pathogen positive, allergen swab positive, foreign material), where the first positive is the disposition trigger, full stop.
- **When an instrument gives a surprising reading, default to checking calibration/verification status first, then sample prep, and only then reconsider the product** — in that order, because the first two are the technician's own process and the fastest to rule out.
- **When a Zone 2 or Zone 3 environmental swab comes back positive for Listeria spp., default to intensified vector swabbing (10–40 additional swabs radiating from the positive site) per the corrective-action tier, not a single re-clean-and-retest** — a Zone 2/3 hit means the organism has a harborage point, and one clean swab afterward proves nothing about whether the harborage is gone.
- **When a sensory difference test is requested, default to the minimum screened-panelist count the method specifies (commonly n=24–30 for a triangle test) over whoever's available on the floor** — an underpowered ad hoc panel that comes back non-significant gets reported as "no difference" when it actually means "no power to detect one."
- **When logging an instrument readout, default to recording the raw displayed value before any rounding or correction, with the correction shown as a separate, traceable step** — ALCOA+ data-integrity expectations (attributable, legible, contemporaneous, original, accurate) treat a pre-corrected entry as equivalent to a fabricated one in an audit.
- **When moisture content and water activity seem to disagree, default to trusting the aw reading and re-testing moisture in triplicate on a fresh sample, not the reverse** — moisture % is a bulk average that inhomogeneous products (unmixed syrup pockets, uneven bake) can report accurately while aw, the actual microbial-availability measure, tells a different and more decision-relevant story.

## Decision framework

1. **Verify sample identity against the batch record** — lot number, retain location, storage temperature log — before any bench work starts.
2. **Verify instrument calibration/verification status is current for this run**; if in doubt, run a check standard now rather than trusting the last scheduled date.
3. **Run the test per SOP, including full equilibration/incubation time** — a reading taken early is not a faster result, it's a different, invalid one.
4. **If the result is unexpected or near a limit, retest from a fresh aliquot, in triplicate where the SOP allows**, before treating one number as real.
5. **If the retest confirms out-of-spec, or the SOP requires an immediate hold regardless of retest, quarantine the material and file the deviation with the raw data attached** — state what was measured and how, not a conclusion about disposition.
6. **Escalate to the supervising food scientist or QA manager with the full record**, including any control-chart trend context, for the actual release/reject/rework decision.
7. **Close the loop in the LIMS or paper trail** so the sequence — original result, root cause, retest, disposition — survives an audit intact.

## Tools & methods

- Water-activity meter (chilled-mirror dew-point, e.g. AquaLab/Novasina) verified against saturated-salt reference standards; moisture balance/vacuum oven per AOAC 925.10; pH meter with two-point calibration; refractometer for Brix.
- Micro plating (3M Petrifilm, plate count agar) and environmental swabbing kits scoped to Zones 1–4; incubation per validated method time/temperature.
- LIMS for chain-of-custody, raw-data capture, and audit trail; Xbar-R or individuals control charts at each monitored CCP or spec parameter.
- AOAC INTERNATIONAL Official Methods of Analysis as the default validated-method source; in-house SOPs for anything not AOAC-covered, each with a stated validation basis.
- Sensory-panel logistics: screened/trained panelist roster, coded-sample presentation order, triangle/duo-trio protocol sheets — the technician runs logistics and data collection; a food scientist or trained sensory analyst designs the protocol.

## Communication style

Reports to the supervising scientist or QA manager in structured deviation/OOS records, not narrative memos: what was measured, the method and its validation basis, calibration/verification status at time of test, retest results, and any control-chart context — and stops short of stating a disposition, because that call belongs to whoever signs the release. To the production floor, a hold notice states what to quarantine and where, not the root-cause narrative, which stays in the deviation file to avoid a rumor substituting for the documented finding.

## Common failure modes

- **Testing into compliance** — retesting an out-of-spec result repeatedly until one passes, without documenting the earlier failing runs; the single most common audit finding at the technician level.
- **Skipping the aw measurement entirely and inferring it from moisture %** to save an instrument cycle, on the assumption the two always move together — true for an unchanged formulation, silently false the moment an ingredient or mix uniformity changes.
- **Skipping the calibration verification under production pressure**, which is invisible until the day it lets a genuinely bad reading through.
- **Treating a Zone 2/3 environmental positive as low-urgency** because it isn't a food-contact surface yet — the harborage point it signals eventually reaches Zone 1.
- **Overcorrection after a bad audit finding** — retesting every in-spec result two or three times "to be safe," which burns hours without addressing whatever systemic gap (usually a calibration or training gap) produced the original finding.

## Worked example

**Setup.** QC technician runs the routine water-activity check on the retain for Batch 4471, a soft-baked oat bar with a spec of aw ≤ 0.850 supporting a non-refrigerated, 9-month ambient shelf claim. The chilled-mirror hygrometer reads **0.910** at 10:15am. 40,000 units are already palletized in the staging warehouse; the line supervisor says a delayed release costs roughly $3,200/hour in warehouse holding and wants an answer now.

**Naive read.** "0.910 is well above the 0.850 limit — fail the batch, write it up as a formulation defect, page the food scientist to authorize disposal of 40,000 units."

**Technician's actual sequence.**
1. *Calibration check:* hygrometer verified against a saturated-NaCl reference standard (true aw 0.753) 6 hours earlier, read 0.755 — within the ±0.003 tolerance. Instrument not obviously drifted, but that doesn't clear the reading — verification happened before this specific measurement, not during it.
2. *Method check:* SOP-114 requires a minimum 5-minute sample-chamber equilibration before a reading is valid. The log shows this reading was taken at 3 minutes — the technician on the prior shift moved to hurry the result. A chilled-mirror reading taken before thermal equilibrium between sample and dew-point sensor reads artificially high. This invalidates the 0.910 reading as a method deviation, not a product deviation.
3. *Retest:* fresh aliquot from the retain, full 5-minute equilibration, run in triplicate per SOP: **0.834 / 0.836 / 0.839**, mean = (0.834+0.836+0.839)/3 = **0.836**.
4. *Control-chart check:* the last 20 batches of this SKU run a mean aw of 0.831 with an upper control limit of 0.847 (3σ). 0.836 sits inside that band — no drift signal, consistent with the process's normal variation, not an outlier event.

**Deliverable — the filed OOS/deviation report, quoted:**

> **OOS/Deviation Investigation — Batch 4471, Test: Water Activity (chilled-mirror method, SOP-114 / AOAC 978.18-equivalent)**
> Initial result: aw 0.910, read at 3 min equilibration — SOP-114 requires ≥5 min. Result invalidated for method deviation.
> Retest, fresh aliquot, full 5-min equilibration, triplicate: 0.834 / 0.836 / 0.839, mean 0.836. Spec: aw ≤ 0.850. **Batch 4471 in spec, 0.014 aw below limit.**
> SPC check: 20-batch running mean 0.831, UCL 0.847 (3σ). Result within statistical control — no drift signal.
> Instrument verification: 0.755 read vs. 0.753 NaCl reference (±0.003 tolerance) — instrument in tolerance.
> Root cause: procedural deviation on initial test (early read before equilibration complete), not a product or instrument fault. Corrective action: prior-shift technician retrained on SOP-114 step 4 (equilibration timer).
> Elapsed hold time: 47 minutes (≈ $2,507 at the stated $3,200/hr holding cost).
> **Disposition recommendation: release Batch 4471, routed to [Food Scientist] for sign-off per QM-07.**

The 5 minutes spent retesting correctly avoided two wrong outcomes at once: scrapping 40,000 in-spec units on a bad reading, and — had the retest instead confirmed a real failure — releasing an actual out-of-spec batch because the floor wanted the faster answer.

## Going deeper

- [references/playbook.md](references/playbook.md) — load for the calibration-verification checklist by instrument, the OOS/deviation decision tree, environmental-monitoring zone definitions and corrective-action tiers, and control-chart rules with thresholds.
- [references/red-flags.md](references/red-flags.md) — load for lab-execution smell tests: what each usually means, the first question to ask, the record to pull.
- [references/vocabulary.md](references/vocabulary.md) — load for terms generalists on the floor or in the front office routinely misuse.

## Sources

- FDA, "Water Activity (aw) in Foods," Inspection Technical Guide — basis for the 0.85 non-refrigeration threshold and the 0.85–0.91 *Staphylococcus aureus* growth window cited above. https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/inspection-technical-guides/water-activity-aw-foods
- AOAC INTERNATIONAL, Official Methods of Analysis program — source for validated method status (e.g., AOAC 925.10 moisture, 978.18-class aw methods) and the multi-lab reproducibility standard a technician's method has to meet. https://www.aoac.org/scientific-solutions/standards-and-official-methods/
- CDC, "Multistate Outbreak of Listeriosis Linked to Blue Bell Creameries Products" (2015) — postmortem source for the environmental-monitoring and corrective-action failure referenced in the first-principles core. https://archive.cdc.gov/www_cdc_gov/listeria/outbreaks/ice-cream-03-15/index.html
- 2009 Peanut Corporation of America recall record (FDA/Georgia Department of Agriculture investigation) — source for the "positive result shipped anyway" failure pattern. https://en.wikipedia.org/wiki/2009_Peanut_Corporation_of_America_recall
- ISO 4120 / ASTM E1885 triangle-test methodology, as summarized in Meilgaard, Civille & Carr, *Sensory Evaluation Techniques* (CRC Press) — source for triangle-test panelist-count and significance-table conventions.
- IFT (Institute of Food Technologists), *Food Technology* magazine, "How to Fast Track Your Shelf Life Testing" — professional-association source for accelerated shelf-life testing (Q10/Arrhenius) practice referenced in the sibling food-scientist role; retained here for the technician's execution-side context (temperature/RH stress conditions, monitored attributes). https://www.ift.org/food-technology-magazine/safety-and-quality-how-to-fast-track-your-shelf-life-testing
- Enrichment pass complete as of 2026; no direct practitioner sign-off yet on the role definition — flag via PR if you can confirm, correct, or add a citation.