Confluence Runbook and How-To Page Quality Audit
Score Confluence how-to and runbook pages from 1 to 5 on clarity, steps, owners and freshness, with fixes for the weakest pages.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Please act as a technical writing reviewer. I will paste the text of [NUMBER_OF_PAGES] how-to or runbook pages from Confluence, each with its title, owner and last-edited date. The reader is someone who is [READER_PROFILE], working under [READER_SITUATION], for example "a new support agent, in the middle of an incident". Score each page from 1 (unusable) to 5 (excellent) on these criteria: Purpose clear in the first two lines; Steps numbered and in a sensible order; Each step names the tool or screen and the expected result; Warnings and rollback shown before the risky step; Owner and last review date visible; Terms explained or linked. Present a scoring table with a column per criterion and a total out of 30, showing the sum. Then, for each page scoring below 20, list its three biggest problems with a quote of no more than 12 words, and rewrite only the first two steps as a demonstration of the improved style. Do not fix the technical content itself; you cannot verify our systems. If a step looks outdated, wrong or dangerous, flag it as [VERIFY] with the question for the owner. Do not add steps that are not in the text. End with a ranked list of pages to repair first, weighing low score against how often the task is likely to occur.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.