A plausible patch can repeat a problem when the underlying state was never examined.
The practical check
Gather the smallest diagnostic evidence that separates competing explanations before changing the system.
Where AI fits
AI can turn reported symptoms into testable explanations and identify the evidence that would distinguish them.
The human decision
People decide which explanation is supported and authorize the repair.
The lesson
A fast fix is more durable when it begins by narrowing what the evidence actually says.
The diagnostic Build Log companion shows the symptom evidence that separated competing explanations ahead of a repair.
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: Turn a complaint into a diagnostic plan
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. Gather the smallest diagnostic evidence that separates competing explanations before changing the system.
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.
