An edited file can look convincing while the real behavior is unchanged.
A fix is marked complete, but the person who reported the problem still sees the old behavior. The change exists. The result has not yet been observed where it matters.
The practical check
Make observed behavior part of the definition of done.
Where AI fits
AI can turn a claimed fix into a short set of visible checks, including the expected result and what remains uncertain until someone looks.\n
The human decision
People perform or approve the real-world check before closing the work.
The lesson
A fix earns confidence when someone observes the intended behavior, not when a change merely exists.
The Build Log companion records visible checks of the reported behavior before the work is closed.
AI Skills
Use this lesson with the AI assistant you already use
Use this to prepare a reviewable next step without changing any system.
Paste the prompt, share only the context needed to answer it, and treat the result as a draft for your review. Do not include confidential information or let an AI assistant make changes without your approval.
Optional: for a visual report and saved memory, run /dxdev first.
Don’t have it? Get it at dxdev.com/skills/dxdev. The prompt works without it.
dxdev LESSON · paste into your AI agent
LESSON: Create a fix verification checklist
WHAT TO SHARE:
A de-identified description of the work, current evidence, and the decision you are considering.
ASK YOUR AGENT TO:
1. Separate confirmed facts from assumptions and unanswered questions.
2. Make observed behavior part of the definition of done.
3. Identify the narrowest useful next review step.
RETURN:
A short table with the evidence, uncertainty, human-owned decision, and next action.
BOUNDARY: Do not change records, contact anyone, route work, publish content, or act in an external system. A person must review the evidence and approve every consequential step.
