# Ask for proof. Then move on.

Set a check before adding more work. Use the reasoning level offered by your tool that fits the task; deeper reasoning and extra agents can use more capacity.

Use in: Codex or Claude Code

Reviewed: 2026-10-09

## Before you start

- The original objective and agreed acceptance criteria.
- The result and the checks actually performed.

## How to use it

1. Paste the objective and the evidence into the prompt.
2. Ask which criteria passed and which remain uncertain.
3. Run only the needed check, then finish when the criteria pass.

## Prompt to copy

Review this result against the original objective. Identify what is verified, what is still uncertain and the smallest next check needed. Do not expand the scope or run unrelated tests. If the agreed checks pass, summarize the result and stop. Objective: [paste]. Result and evidence: [paste].

## A practical example

Illustrative scenario, not a measured case study.

A button fix passed a reproduction of the original bug. Record that evidence; do not assume it proves the entire payment journey or add unrelated work.

## Check the result

- Every claim of success has supporting evidence.
- Untested behavior remains explicitly unverified.
- The next check is relevant to an unmet criterion.

INMC example. A clearer scope can reduce avoidable rework; no fixed usage saving is promised.

## Official reference

[Claude Code · Best practices](https://code.claude.com/docs/en/best-practices)



[Back to the library](https://ineedmycredits.com/smarter-usage)

Canonical HTML: https://ineedmycredits.com/smarter-usage/verify