Confluence Documentation Coverage Gap Audit for a Product
Compare documentation to product features and find gaps.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Check documentation coverage. Product features or processes: [FEATURE_LIST]. Existing Confluence pages by title and last updated: [PAGE_LIST]. Common support questions: [SUPPORT_QUESTIONS]. Audience: [AUDIENCE]. Latest changes per feature: [LATEST_CHANGES]. Last quarter's coverage share, if any: [LAST_QUARTER]. Writers available: [AVAILABLE_WRITERS]. State the date of the page list and the product version compared. Work through the features in the order given. For each, say which pages you matched and why, so I can correct a wrong match, and mark coverage full, partial, outdated or missing. Treat a page as outdated only if its date is older than the latest change I mention; where one page covers many features, mark coverage partial unless it explains each one. Where a title does not tell you what a page covers, say you could not judge. Rank gaps with a simple score and show it: support questions per month, times a risk factor of 1 to 3 that I will confirm, plus one point if the feature is new this quarter. List the weights as assumptions the team can argue with, and offer an alternative ranking using support volume only to see whether the order changes. Return a coverage matrix, the share of features with full coverage compared with last quarter, a plan for the ten most valuable pages to write or update (owner placeholder and one-line outline), a plan for the first two weeks that fits the writers available, and a one-paragraph summary for the head of the team.
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.
See an example result (fictional data)
Invented table. Feature: Invoice export | Pages: "Exporting invoices" (updated 8 months ago) | Coverage: outdated | Support questions per month: 22 | Priority: high. Feature: Team permissions | Pages: none | Coverage: missing | Support questions: 15 | Priority: high. Feature: Dark mode | Pages: "Display settings" | Coverage: full | Priority: low. Full coverage: 6 of 20 features = 30 percent. Priority arithmetic: score = questions per month x risk factor (1 to 3). Invoice export 22 x 2 = 44. Team permissions 15 x 3 = 45. Dark mode 2 x 1 = 2. Ranking: team permissions first, then invoice export. Next step: write the permissions page this week and update the export page next, with an owner and a review date on each.
Illustrative only, made-up data. Your results will differ and must be reviewed.