01
Match the claim to the evidence
You separate the proposed repair from the facts and identify which findings directly support it.
Made for Auto Mechanics
Check Your Evidence Before Recommending a Repair
10 min
Beginner
Decisions
Build Professional Skills
You match each proposed repair to a verified symptom, test result, measurement, code, inspection finding, or service specification before you discuss price.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Avoid turning a clue into a conclusion.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Apply the evidence gate
You check the status assigned to each repair and reject conclusions based only on a code, symptom, or guess.
03
Prepare the recommendation
You turn the supported finding into a short explanation without overstating cause, urgency, or certainty.
Make Your Play
Check Your Evidence Before Recommending a Repair
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Provide the year, make, model, mileage, engine or trim details, and any recent work that affects the concern.
0/10000
State what was reported and note whether you verified the symptom.
0/10000
List your tests, readings, codes, visible wear, and inspection findings without adding an unconfirmed cause.
0/10000
Enter the repair you are considering before presenting a price.
0/10000
Provide the applicable limit, test procedure, bulletin, or service information when available.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Match the claim to the evidence
You separate the proposed repair from the facts and identify which findings directly support it.
02
Apply the evidence gate
You check the status assigned to each repair and reject conclusions based only on a code, symptom, or guess.
03
Prepare the recommendation
You turn the supported finding into a short explanation without overstating cause, urgency, or certainty.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
You paste your notes as written. You should include actual readings, test outcomes, code numbers, and visible conditions when available. You shouldn’t fill gaps with assumptions. If the result says “More testing needed,” you complete the named check before making the recommendation.
Advanced instructions
You can run each proposed repair separately when several faults overlap. You can also compare your measurements with service limits, check whether the test isolates the failed part, and challenge any urgency claim that isn’t tied to a documented risk.
Use this when
You have inspection or diagnostic findings and need to decide whether the evidence is strong enough to recommend a repair.
You'll need
- Vehicle context
- Reported symptom
- Tests and findings
- Proposed repair
- Service information or specifications
You'll get
- A status for every proposed repair, direct evidence for every supported claim, a specific next check for every evidence gap, and customer wording that doesn't overstate the findings.
By the end of this playbook
You will have:
- A status for every proposed repair, direct evidence for every supported claim, a specific next check for every evidence gap, and customer wording that doesn't overstate the findings.
Examples
Progress 1 of 3