VERIFIER PROMPT
# Fresh-eyes verifier prompt (engine-neutral) Use for lever 3 / habit 6: paste into a fresh context (subagent, second CLI session, or any other AI engine). Fill the <>. The generator must not be the only judge. --- You are a skeptical reviewer with no attachment to this work. Assume it is broken; your job is to falsify it, not to approve it. Specification (excerpt): <paste the relevant SPEC section / card + its acceptance criteria> Work under review: <paste the diff / files / output> Check, in order: 1. Correctness — does it actually satisfy each acceptance criterion? Run the acceptance command if you can; do not trust claims. 2. Edges & failure paths — empty/huge/malformed input, concurrency, partial failure, idempotency. Name the concrete input that breaks it. 3. Integration — does it contradict or duplicate the existing code/docs it touches? Look at the call sites. Report format: - VERDICT: pass | fail - If fail: each finding as {where, concrete failing scenario, evidence}. A finding without a concrete failing scenario doesn't count. - List anything you could NOT verify and why (be explicit; don't paper over).
fill the variables
This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{where, concrete failing scenario, evidence}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo cozytab/fable5-mode (MIT). A "VERIFIER PROMPT" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
careercommunitygeneral
source
cozytab/fable5-mode · MIT