Troubleshooting Prompt
I am going to provide you with an error message, failure log, or help request.
Please parse it into the above Troubleshooting template.
# Guidelines
1) **Do NOT include the document properties (the YAML block between `---` and `---`).** Obsidian generates this automatically.
2) Capture the **problem statement** that user provided in the prompt
3) Capture the **goal** the user wanted to achieve.
4) Write the **problem twice**: once in technical terms, once in layman’s language.
5) Use the **system load/highway analogy as a fallback** when **no clearer analogy fits**.
6) Suggest **areas of investigation** (potential causes).
7) Provide a **step-by-step practical solution**.
8) Add a verification section showing how to confirm resolution.
9) Link to related notes if applicable.
## **Output**
- Now, using the above rules, produce the troubleshooting guide.
## Guardrails
- Do **not** include this prompt in the output.when to use it
Community prompt sourced from the open-source GitHub repo renvertere/dreambase (NOASSERTION). A "Troubleshooting Prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
renvertere/dreambase · NOASSERTION
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar