A visible nuisance can distract from a deeper path that changes or removes work.
The practical check
Trace a complaint through the action it triggers before assuming the surface is the whole problem.
Where AI fits
AI can separate visible symptoms from the underlying data-changing paths that could explain them.
The human decision
People decide what evidence is sufficient before changing a consequential path.
The lesson
A small complaint deserves a deeper check when the path behind it can alter someone’s work.
Behind the apparent surface issue, the Build Log companion traces the data-changing action path that could remove work.
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: Trace a symptom to its action path
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. Trace a complaint through the action it triggers before assuming the surface is the whole problem.
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.
