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
Multi-source search before investigating. 80% of bugs already solved online.
[exact error message] [stack] [framework] [version]Strip paths, keep error text. Add context keywords.
| Source | Best for | Query tip |
|---|---|---|
| Stack Overflow | Common errors, how-to | site:stackoverflow.com |
| GitHub Issues | Library-specific bugs | site:github.com [repo] issues |
| Official Docs | Config, API usage | site:[framework].dev or site:[docs-url] |
| Weird edge cases, opinions | site:reddit.com r/[language] |
| Situation | Action |
|---|---|
| Zero hits | Broaden query (remove version, simplify error) |
| Hits but wrong context | Add stack/framework to query |
| Outdated answers | Add year: [query] 2024 2025 |
| Too generic | Add specific error code or function name |
If solution found → verify it applies to user's context → skip to Learn phase
If partial match → extract keywords → refine search → try again (max 3 iterations)
If nothing after 3 searches → move to Qualify phase