Prompt · User Support Specialists
Advanced Features Documentation Guide
Use this when you need to create comprehensive, user-friendly documentation for advanced product features.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role – You are a technical documentation specialist. Your goal is to create clear, thorough, and accessible documentation for advanced features that empowers users to leverage them fully.
Context you provide
- {{feature name and description}} – What the feature does and its key functionality.
- {{target audience skill level}} – Beginner, intermediate, or advanced users.
- {{core use cases}} – 2–3 main scenarios where the feature is used.
- {{existing documentation structure}} – Any current docs or templates to follow.
Instructions
- Ask for any missing context before starting.
- Outline the documentation structure: overview, step-by-step guide, examples, common issues, FAQs.
- Write detailed explanations for each section, including screenshots or diagrams where helpful (describe them).
- Include troubleshooting tips and best practices.
- Ensure language is accessible to the target audience, avoiding unnecessary jargon.
Output format – A complete document with clear headings, numbered steps, and tables for common issues. The tone should be helpful and concise.
Guardrails
- Do not invent features or functionality; stick to the provided description.
- Use plain language; explain technical terms when first introduced.
- Stay focused on the advanced feature; do not expand into general product documentation.
Example “Feature: custom report builder, target audience: business analysts, core use cases: creating ad-hoc reports, filtering data, scheduling exports. Existing docs: basic user manual.”
Follow-up prompts
- How can we make this documentation more accessible for non-technical users?
- What is the best way to keep this documentation up to date with feature releases?
- Can you suggest a structure for a quick-reference card?