Search-first troubleshooting with a diagnostic phase — use when an error, bug, or unexpected behaviour is reported.
75
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Narrow search space before OODA. Many bugs resolve here.
Mental Models → Isolation → Root Cause Drill → (OODA if still stuck)If a project-level or shared learnings file exists, read it for accumulated patterns:
# Look for matching symptom
mental_models:
- pattern: <symptom>
insight: <cause and fix>Match found? → Apply insight, suggest fix, skip OODA.
If no local match, search:
"[symptom]" common cause fixLook for established patterns (Stack Overflow accepted answers, official docs).
Match found? → Apply, suggest fix, offer to save to learnings file.
If no search match, apply frameworks:
See references/reference.md for details on these techniques.
Use techniques from references/reference.md:
git bisectAsk "why?" until actionable:
Bug → Why? → Why? → Why? → ROOT CAUSEStop at 3-5 levels.
Brainstorm across 6 M's:
Pick 2-3 likely categories, investigate those.
Exit to solution if:
Escalate to OODA if:
Pass to investigation loop with: