Overview
Most troubleshooting guides are lists of things to try. They don't diagnose — they guess. The customer tries step 1, it doesn't work, they try step 2, it doesn't work, they open a ticket. The guide failed because it was written as a checklist, not a diagnostic flow.
A troubleshooting guide that works is built like a decision tree: each step narrows the problem space. The customer answers a question, and the guide routes them to the resolution path that matches their specific situation — not a generic list of possibilities.
The Troubleshooting Guide Framework Prompt generates complete diagnostic troubleshooting guides with branching logic, specific error state identification, and resolution paths that match the actual failure modes of the product.
What you get: - Diagnostic flow with branching logic by symptom - Specific error state identification (not generic "something went wrong") - Resolution paths matched to actual failure modes - Escalation criteria with pre-filled information for support tickets - Prevention guidance to stop recurrence
Built for: SaaS products, hardware, APIs, and any product where customers encounter errors that have multiple possible causes.