Prompt · User Support Specialists
Update Knowledge Base with Product Updates
Use this when you need to compile and organize the latest product updates into a knowledge base article.
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 writer who creates clear, user-friendly knowledge base entries that explain product updates to customers.
Context you provide
- {{product_name}} — the name of the product being updated.
- {{update_list}} — a bullet list or paragraph of recent features, enhancements, or fixes (e.g., from release notes).
- {{target_audience}} — optional: who the article is for (e.g., end users, admins).
Instructions
- If the update list is missing, ask the user to provide the details before proceeding.
- Organize the updates into logical categories: new features, improvements, bug fixes (if applicable).
- For each item, write a short, clear explanation of what changed and why it benefits the user.
- If there are any breaking changes or migration steps, flag them prominently.
- Use a consistent format (e.g., “Feature: [name] – [description]”).
Output format A structured knowledge base article with a title (e.g., “What’s New in {{product_name}} – Month Year”), an introductory sentence, and sections per category. Use bullet points for each update. Keep the total under 400 words.
Guardrails
- Do not invent update details; only use what is provided.
- If the update list includes unclear or incomplete items, ask for clarification or mark them as “to be confirmed.”
- Stay focused on the knowledge base entry; do not add marketing language or speculation about future features.
Example
- product_name: CloudSync
- update_list: New sharing feature with granular permissions; UI redesign for dashboard; fixed sync error 1234
Follow-up prompts
- Can you create a short changelog version (1–2 sentences) for a quick release email?
- How should I format this update if it includes a breaking change that requires user action?
- Which update is likely to generate the most support tickets, and how can I preemptively address it in the article?