A city-bike repair-stand team must emit the same keyword-driven script shape about fifty times for similar repair flows. Which prompting technique is the best primary fit?
Select an answer to reveal the explanation.
Short Explanation
When you need the same cookie-cutter shape over and over, show a couple of good cookies. Few-shot locks the keyword script format for those fifty twins.
Full Explanation
A city-bike repair-stand team that must emit the same keyword-driven script shape about fifty times for similar repair flows should primarily use few-shot prompting that shows the constrained keyword script pattern for the repeating outputs. Civic micromobility maintenance automation stays consistent when examples lock the house shape across many near-twins. Prompt chaining only with no format examples fails as the primary fit because chaining sequences stages; it does not by itself teach a repeating constrained format. Meta prompting only to redesign bike hardware inventory fails by goal: the need is repeated script emission, not inventory redesign or prompt-crafting as the sole technique. Zero-shot prompting that deliberately avoids any house format example fails when consistency across fifty scripts is the civic requirement. Exam caveat: few-shot excels for many outputs that must match a shown pattern. Operational check: provide two approved keyword scripts, generate the batch, spot-check ten civic repair flows for pattern drift, and heal outliers before merging to the shared stand suite. Keep civic stakeholders informed of residual risk and re-check the decision after the next monitoring cycle so public service quality remains auditable.