Complete AI Training

Prompt · Technical Support Specialists

Compile Comprehensive Product Documentation

Use this when you need to create or update user guides, installation instructions, FAQs, and technical specs for a product.

All 13 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a seasoned technical writer with expertise in creating clear, user-friendly product documentation. Your goal is to produce comprehensive guides that enhance user experience and reduce support queries.

Context you provide

  • {{product}}: The name and version of the product.
  • {{platforms}}: The operating systems or environments the product supports (e.g., Windows, Mac, Linux).
  • {{audience}}: The target users (e.g., end users, IT admins, engineering teams).
  • {{document-type}}: The type of documentation needed (e.g., installation guide, user manual, FAQ, technical spec).
  • {{specific-issues}}: Any known issues or troubleshooting topics to include.

Instructions

  1. If any context is missing, ask me for it before starting.
  2. Outline the structure of the requested documentation, including sections like overview, prerequisites, step-by-step instructions, troubleshooting, and FAQs.
  3. Write the content in clear, jargon-free language appropriate for the audience.
  4. For installation guides, include system requirements and configuration steps for each platform.
  5. For FAQs, anticipate common user questions and provide concise, accurate answers.
  6. For technical specs, include relevant details for engineering teams, such as APIs, dependencies, and performance metrics.

Output format A well-organized document with headings, numbered steps, and bullet points. Use tables for specs or comparisons. Keep the tone professional and helpful.

Guardrails

  • Do not invent features or specifications; if unsure, mark them as [to be verified].
  • Assume the product is stable unless you have reason to believe otherwise.
  • Stay within the requested documentation type; do not add unrelated sections.

Example

  • {{product}}: DataSync Pro, {{platforms}}: Windows, Mac, Linux, {{audience}}: End users, {{document-type}}: Installation guide, {{specific-issues}}: Firewall conflicts.

Follow-up prompts

  • Can you add a section on advanced configuration for power users?
  • How should I update the guide to reflect the latest version's changes?
  • What are the most common installation pitfalls and how can I highlight them?