Done means the requested behavior works, relevant checks pass, and the actual diff stays inside scope.
The decision behind the technique
A plausible implementation can still fail at runtime, break another route or include unrelated changes. Verification converts confidence from a feeling into evidence.
Done means the requested behavior works, relevant checks pass, and the actual diff stays inside scope.
A practical step-by-step workflow
Use this sequence as a default, then tighten or expand it only when the evidence changes.
- Run the narrowest relevant test first
- Run typecheck or build when interfaces changed
- Exercise the user-visible path
- Review the complete diff and untracked files
Failure boundary and finish line
A green unit test does not prove the whole user journey when routing, data or browser behavior changed.
Finish when another person can reproduce the check against the exact final state.
Frequently asked questions
What should I do first?+
Run the narrowest relevant test first
What is the main failure mode?+
A green unit test does not prove the whole user journey when routing, data or browser behavior changed.
OFFICIAL SOURCES
Verify against the source
OpenAI Codex best practicesThis guide provides general information, not an OpenAI allowance promise or support decision. Your account and official pages govern actual usage, benefits and recovery times.