A court clerk finds that vague prompts like "fix this" yield unusable continuance letters compared with specific role and format asks. What prompt principle is illustrated?

The court clerk's experience that vague prompts like "fix this" produce unusable continuance letters illustrates specificity as a core prompt-engineering principle. Civic drafting needs clear role (e.g., court clerk assistant), task (draft a continuance letter), and format (parties, hearing date fields, formal closing). Specificity reduces ambiguity, raises first-pass usability, and makes review faster because the draft already matches institutional norms.

Providing prior approved continuance letters as few-shot examples is not what the scenario illustrates: the clerk’s problem is the underspecified initial prompt, not a lack of examples, and few-shot samples do not replace the need for clear role, task, and format instructions. Refining initial clerk drafts through follow-up clarification prompts is not the principle at issue: the scenario contrasts a vague opening ask with a specific one, showing that the first prompt should already name role, task, and format rather than relying on later clarification. Lowering model temperature settings is not the illustrated principle: temperature controls randomness in generation, whereas the clerk’s example shows that prompt specificity—role, task, and format—drives usable output.

Exam caveat: specificity is not the same as pasting confidential case facts into an unapproved tool; specificity of instructions can coexist with privacy redaction. Operational check: maintain approved prompt skeletons for common filings that name role, required sections, and "do not invent dates or docket numbers"; compare vague versus specific trials on the same letter and retain the specific pattern in the clerk playbook.