Back to Prompt Library
evaluation
Review evidence and failure behavior
Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.
Linked challenge: Build a Water Repair Evidence Packet
Format
Text-first
Lines
4
Sections
1
Linked challenge
Build a Water Repair Evidence Packet
Prompt source
Original prompt text with formatting preserved for inspection.
4 lines
1 sections
No variables
0 checklist items
Review the implementation against this contract: A complete packet needs invoice, completion record, and matching asset identifier. Do not infer a missing record. Test this domain failure: Supply a signed page for another project. A signature alone must not establish completeness. Check input citations, calculations, and actual tool logs. Report unsupported claims and unexecuted tests. Do not approve external actions.
Adaptation plan
Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.
Keep stable
Preserve the source structure until you know which part of the prompt is actually driving the result quality.
Tune next
Change domain facts, examples, and tool context first before you rewrite the instruction scaffold.
Verify after
Validate one failure mode at a time so prompt changes stay attributable instead of getting noisy.