Create systematic troubleshooting guides for technical issues

Troubleshooting Guide Creator creates comprehensive, structured troubleshooting guides with clear diagnostic steps, solutions, and escalation paths for technical issues, helping users systematically diagnose and resolve problems by breaking them into logical steps with clear diagnostic criteria and multiple solution paths. Core principles: a problem-centric structure, clear problem statements and symptoms, if-then decision-tree logic, solutions prioritized by likelihood and impact, and both quick fixes and comprehensive solutions; a user-experience focus, writing for the target audience's skill level, consistent formatting, scannable visual cues, and time estimates per step; and a systematic approach, a diagnostic sequence from simple to complex, verification after each solution, rollback instructions where applicable, and documented escalation triggers.

Use it to write a troubleshooting guide following the standard structure: symptoms with exact error-message text, quick checks for the most common cause, numbered diagnostic steps each stating what to check, the expected result, and the branch to take if normal or abnormal, solutions with usage conditions, action steps, verification, and a rollback, a prevention section, and an escalation section naming who to contact and what information to provide. It documents specific diagnostic techniques: a layer-by-layer approach for network issues (physical, network, application layers in sequence), a binary-elimination method for performance degradation (test minimal configuration first, add components incrementally), decision trees for complex multi-branch issues like database connection failures, and log-analysis guidance covering error-pattern recognition, key log locations, and commands for counting error types or filtering a time range. It also documents a probability-weighted error-message writeup pattern - stating the meaning of an error and the approximate share of cases attributable to each common cause - and a quality checklist to run before publishing, plus ongoing maintenance guidance covering quarterly review, screenshot updates, and tracked success-rate metrics.

Input is a technical problem or class of problems that needs a troubleshooting guide, plus its common causes and known fixes. Output is a structured Markdown guide: symptoms, quick checks, numbered diagnostic steps with expected results and branching, solutions with verification and rollback, a prevention section, and an escalation section - optionally including a layer-by-layer or binary-elimination diagnostic flow, a Mermaid decision-tree diagram for complex issues, platform-specific command examples (Linux/Mac and Windows), and log-analysis commands for finding and counting errors.

Meaning: The target server is not accepting connections on the specified port.

Common Causes:

1. Service not running (70% of cases)
2. Firewall blocking port (20% of cases)
3. Wrong port number (10% of cases)

Diagnostic Commands:

# Check if port is listening
netstat -tulpn | grep :80

# Test connectivity
telnet server.com 80

This is the documented error-message writeup pattern: meaning, ranked common causes with approximate frequency, and the exact diagnostic commands to run. Other documented commands span `systemctl`/`journalctl` on Linux, `Get-Service`/`Get-EventLog` on Windows, `ping`/`ipconfig`/`telnet` for network layers, `grep`/`sed` for log filtering, and a Mermaid `flowchart` for decision-tree diagrams. No specific ticketing or knowledge-base platform integration is documented; the guide is Markdown meant to be published into whichever documentation system a team already uses.

Technical support, SRE, and documentation teams writing troubleshooting guides for recurring technical issues who want a systematic, verifiable diagnostic structure with escalation paths, rather than an unstructured list of possible fixes.