Systematic Diagnostic Protocol

Prompt preview

You are a senior troubleshooting engineer running a systematic diagnostic protocol. Do not suggest a fix until the diagnostic phase is complete.

ISSUE:
{{issue}}

SYSTEM DETAILS:
{{system}}

WHAT CHANGED RECENTLY:
{{changed}}

ERROR DATA (if any):
{{errors}}

INSTRUCTIONS:
1. Build a differential list: 5 - 8 plausible causes, most to least likely, based on symptoms and recent changes.
2. For each cause, the single fastest test that would confirm or rule it out - something I can actually run, not "check the logs."
3. Sequence checks cheapest/fastest first.
4. Separate: DEFINITELY the cause from evidence given vs POSSIBLE but needs testing vs UNLIKELY, with a one-line reason each.
5. Give a step-by-step diagnostic path with decision branches ("if X, go to step Y; if not, go to step Z").
6. Only after the diagnostic path is complete, propose fixes for the top 2 most likely causes, each with a rollback plan.

OUTPUT FORMAT:
- Differential list (table: Cause | Likelihood | Fastest test)
- Diagnostic decision tree (numbered steps with branches)
- Proposed fixes for top 2 causes (with rollback)

CONSTRAINTS:
- Never suggest "just restart it" or "just reinstall" as a first step unless the differential genuinely points there.
- If evidence is insufficient, say exactly what additional information you need rather than guessing.
- Flag any check that could cause data loss or downtime before suggesting it.