A food-coop membership tester uses few-shot prompts filled with grocery-website examples to perform a first-time, multi-step coverage analysis of a produce-share rule. What is the best assessment of that choice?
Select an answer to reveal the explanation.
Short Explanation
Wrong-aisle examples won’t save a brand-new, multi-step coverage job. Prefer chaining with checks, and meta if you still need help writing the ask.
Full Explanation
Using few-shot prompts filled with grocery-website examples for a first-time, multi-step coverage analysis of a food-coop produce-share rule is a poor primary fit. Prefer chaining for precision with verification and/or meta prompting because the civic task is new and multi-step, while off-domain grocery exemplars can mis-steer coverage logic for membership shares. Claiming few-shot with any examples is always best for multi-step coverage analysis fails because technique choice depends on task structure and example relevance. Switching to metamorphic testing of the coop’s recommendation model fails by concept: the need is application coverage analysis prompting, not metamorphic evaluation of a recommender. Dropping all GenAI to measure only neuron coverage of the membership chatbot fails similarly by shifting to LLM-as-SUT white-box metrics. Exam caveat: few-shot helps repeating formats with good examples; novel multi-step analysis usually wants chaining and/or meta prompting. Operational check: craft a meta prompt for the produce-share coverage ask, chain verified hops against coop rules, refuse grocery exemplars that conflict with civic share policy, and record why few-shot was deferred until blessed in-domain samples exist.