Troubleshooting Guide

Create a Troubleshooting Guide tailored to your inputs.

Prompt template

You are a technical support expert. Generate a comprehensive troubleshooting guide in Markdown for the following issue.

Product: {{product_name}}
Issue Title: {{issue_title}}
Issue Description: {{issue_description}}
{{affected_users}}
{{symptoms}}
{{environment}}
{{already_tried}}

Create a detailed troubleshooting guide with these exact sections:
1. ## Overview — brief summary of the issue and scope
2. ## Prerequisites — checklist of what the user needs before starting
3. ## Diagnostic Steps — numbered steps to identify root cause
4. ## Step-by-Step Resolution — concrete numbered steps to fix the issue, with code blocks where relevant
5. ## Verification — how to confirm the fix worked
6. ## When to Escalate — conditions that require escalation and who to contact

Use Markdown formatting with headers, bullet points, numbered lists, and code blocks where appropriate. Be specific and actionable.

Fill the 7 fields below to customize.

Customize before copy

Fill these — your prompt updates live.

Stays in your browser. Nothing sent anywhere — we don't run a server for this.

Product Name*{{product_name}}

Issue Title*{{issue_title}}

Issue Description*{{issue_description}}

Affected Users*{{affected_users}}

Symptoms*{{symptoms}}

Environment*{{environment}}

Already Tried*{{already_tried}}

Using Gemini, Llama, Mistral or local LLMs? Copy the prompt and paste — no deep-link supported.

Sample

Example output

What the prompt produced when KLI ran it for a real case. Yours will vary by model and inputs.

## Overview

This troubleshooting guide addresses the reported issue and provides structured steps to diagnose and resolve it.

**Affected Component:** Application / Service Layer
**Severity:** Medium
**Last Updated:** ${new Date().toISOString().split("T")[0]}

---

## Prerequisites

Before beginning, ensure you have:

- [ ] Administrative or appropriate access to the system
- [ ] Access to application logs
- [ ] A backup of any critical data
- [ ] The version/build number of the affected software

---

## Diagnostic Steps

1. **Verify the issue is reproducible**
   - Attempt to reproduce the issue in a controlled environment
   - Note exact conditions: time, user actions, and system state

2. **Check system logs**
   - Review error logs for relevant timestamps
   - Look for any correlated errors or warnings

3. **Identify scope**
   - Determine if the issue affects all users or a subset
   - Check if the issue is environment-specific (dev/staging/production)

4. **Review recent changes**
   - Check deployment history for recent releases
   - Review configuration changes in the past 24–48 hours

---

## Step-by-Step Resolution

### Step 1: Clear Application Cache

\

API Documentation

Create a API Documentation tailored to your inputs.

Operations

Bug Report Formatter

Create a Bug Report Formatter tailored to your inputs.

Operations

Changelog Writer

Create a Changelog Writer tailored to your inputs.

Operations

Agency Agreement

🇮🇳

Draft a Agency Agreement tailored to your inputs.

Legal & Contracts

Made with KLI — extracted from real tools, shared free. krakelabsindia.com

Fill these — your prompt updates live.

Example output

You might also like