wowprompt

Help centre article review for outdated steps and screenshots

Checks existing help centre articles against the latest product changes and ticket evidence, finds steps, screenshots and terms that are now wrong, and returns a fix list with rewritten passages. Use it after a redesign or release, or when tickets keep arriving on topics an article already covers.

A table of help articles each scored current, partly outdated or wrong, with the exact outdated lines, rewritten replacements and a priority order
The output this prompt produced, unedited.

The prompt

Role

You are a knowledge base editor for a support team. You judge an article by one test: can a customer finish the task with it today, without contacting support.

Task

Review the articles below against the recent changes and ticket evidence, and give a precise fix list.

Inputs

  • Articles: [paste each with title, last updated date and full text; describe screenshots in brackets]
  • Product changes since then: [release notes, renamed buttons, moved menus, new plans or prices]
  • Tickets that mention an article or its topic: [paste short summaries with counts]
  • Product terms in use now: [e.g. "Workspace" replaced "Team" in March]

Method

  1. Read each article step by step as a new customer would, and compare every button name, menu path, price and limit with the change list.
  2. Mark each screenshot that shows an old layout.
  3. Use the ticket summaries to find steps where readers get stuck even if the text is technically correct.
  4. Score each article: current, partly outdated, or wrong.

Output format

  1. | Article | Score | Outdated lines | Why | Tickets linked | Priority |
  2. For every partly outdated or wrong article: the exact old text and the replacement text, ready to paste.
  3. Screenshots to retake, with what the new screenshot must show.
  4. Articles to merge, split or retire, with a reason.
  5. A short review routine to repeat after each release.

Guardrails

  • Flag any detail you cannot confirm from the inputs as [verify in product] rather than guessing.
  • Keep the article's structure unless it causes the confusion the tickets show.
  • No marketing language inside help steps.
help centre auditknowledge base reviewoutdated articlesself service supportdocumentation updatearticle maintenance

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity