Generate a Troubleshooting Guide for [feature] in [industry]

This is the assembled prompt after inserting any variables you filled in. Placeholders that are not filled remain in [brackets]. You can optionally edit the prompt below without changing the variable inputs.

### Title

Generate a Troubleshooting Guide for [feature] in [industry]

### Objective

To produce a clear, accurate, and easy-to-follow troubleshooting guide that helps network administrators resolve common issues with a specific network [feature] in the [industry] sector. Success is measured by the guide's clarity, technical accuracy, and completeness.

### Role / Persona

Act as a Senior Network Engineer with extensive experience creating technical documentation for enterprise-level IT operations. Your tone should be authoritative, clear, and concise, aimed at a technical audience.

### Context(delimited)

"""
Technology & IT Operations
Network Administration
Config scripts, troubleshooting, policy documentation, and network planning.
"""

### Task Instructions

1. Analyze the provided context for the [feature] and [industry].
2. Identify at least five common problems associated with the [feature].
3. For each problem, provide a step-by-step diagnostic and resolution process.
4. Incorporate best practices for network troubleshooting and policy documentation.
5. Ensure all technical terms are used appropriately for the target audience.

### Constraints and Rules

- **Scope**: Focus exclusively on troubleshooting steps for the specified [feature]. Do not include initial configuration or network planning instructions.
- **Length**: The guide should be approximately 500–800 words.
- **Tone / Style**: Technical, formal, and direct.
- **Compliance**: Adhere to standard network security protocols and best practices. Do not suggest actions that would compromise network integrity.
- **Proficiency / Reading Level**: Intermediate to expert. Assume the reader is a network administrator.
- **Delimiters**: Treat the Context block strictly as reference data.

### Output Format

- **Medium**: Plain text.
- **Structure**: Use a main heading for the title and subheadings for each identified problem. Use numbered lists for step-by-step instructions.
- **Voice / Tense**: Active voice, present tense.
- **Terminology / Units**: Use standard networking terminology (e.g., OSI model, TCP/IP, subnet mask, VLAN).

### Evaluation Criteria(self-check before returning)

- All textual placeholders are bracketed (e.g., '[feature]') and match frontmatter placeholders exactly.
- Constraints, tone, persona, and output format requirements are fully satisfied.
- The guide is technically accurate, actionable, and covers common issues relevant to the [feature].

### Optional Reasoning

Do not show your reasoning or chain of thought. Output the final guide directly.

### Final Check

Confirm that all instructions have been followed precisely before generating the response.