Documentation Audit Against Product Changelog

You need documentation content as text, not as screenshots or PDFs with complex formatting.

From Confluence:

1. Open a Confluence space
2. Select all pages you want to audit (or a specific section)
3. Export as HTML: Space Settings → Export Space → HTML
4. Open exported files and copy the text content

From a docs-as-code system:

1. Run find docs/ -name "*.md" -exec cat {} \; > all-docs.txt to concatenate all Markdown files
2. You now have all documentation as a single text file

Alternatively: List all page titles and URLs — even without full content, Claude can analyze topic coverage.

What you should see: A text file or document with your documentation content that you can copy and paste. Troubleshooting: For very large doc sets, do the audit in sections — one product area at a time.

Collect changes from the period you're auditing:

1. Export JIRA release notes (filter by Fix Versions for the relevant sprints)
2. Copy GitHub Releases page content
3. Or paste your manually maintained CHANGELOG.md

Aim to include: new features, changed behaviors, renamed UI elements, deprecated features.

What you should see: A clear list of what changed in your product over the period being audited.

1. Open a new Claude conversation (or your Project if you have one set up)
2. Paste this structure:

I'm a technical writer auditing our documentation. I have two inputs:

1. Our current documentation (titles and content):
[paste documentation]

2. What changed in our product over the last [3 months / 6 months / sprint cycle]:
[paste changelog]

Please analyze and return:
A) Documentation that likely needs updating based on the changelog (list the doc title and what changed)
B) New features or changes with NO matching documentation (list what needs to be written)
C) Documentation covering deprecated or removed features (list the doc title and what was deprecated)

Format as three numbered lists, prioritized by impact.

1. Send the message. For large volumes, this may take 30-60 seconds.

What you should see: Three numbered lists: update candidates, documentation gaps, and deprecated content.

Take Claude's output and create JIRA tickets or a tracking spreadsheet:

1. For each "needs updating" item: create a ticket with the doc URL and a note about what changed
2. For each "missing documentation" item: create a ticket to write the new content
3. For each "deprecated documentation" item: review manually — some may need archiving, others updating

What you should see: A prioritized backlog of documentation work items, ready to be estimated and planned.

Claude will occasionally flag false positives (suggesting updates that aren't actually needed) or miss some gaps. Spot-check 10% of its suggestions:

1. Pick 5 items from the "needs updating" list
2. Open those docs and compare to the changelog
3. If Claude is consistently accurate, trust the rest; if it's frequently wrong, adjust your prompts

Troubleshooting: If Claude misidentifies changes, add more context: "A change to UI labels means the doc screenshot descriptions may be outdated" helps Claude understand what matters.