See it in action

What it is

The knowledge proofreader workflow keeps your documentation honest by cross-referencing articles against what your team is actually saying. Give it an article from your knowledge base, and it fetches the content, breaks it into core claims and concepts, then hunts through your Slack threads, Intercom tickets, and Linear issues for anything that contradicts, updates, or expands on what's written. It delivers a structured gap analysis showing exactly what's missing, outdated, or wrong—with links to the sources that prove it.

What it solves

Documentation rots silently. Your team ships a feature update, discusses a policy change in Slack, or resolves a support pattern in Intercom—but nobody updates the help article. Customers read outdated instructions and file tickets. New hires follow procedures that changed three months ago. The knowledge base becomes a museum of how things used to work, and nobody knows which articles to trust anymore.

This workflow catches the drift before it causes damage. Instead of waiting for a customer to complain or a new hire to get confused, it proactively scans for gaps between what your docs say and what your team actually knows. It turns the invisible problem of knowledge decay into a concrete, prioritized list of fixes.

How it works

Super starts by fetching the article you want to analyze—just provide a name, link, or ID. It reads the full content and identifies the core concepts, claims, processes, and facts that make up the article.

Then it fans out across your team's activity. It searches recent Slack threads for discussions that relate to each concept—maybe someone mentioned a workflow change or flagged an edge case. It checks Intercom tickets for recurring customer questions that suggest the article is missing something obvious. And it scans Linear issues for completed features, bug fixes, or product changes that may have shifted how things actually work compared to what the article describes.

Finally, it compiles everything into a detailed gap analysis table. Each row identifies a specific issue—whether information is missing, outdated, or inaccurate—rates its importance from critical to low, explains what needs to change, and links directly to the Slack messages, tickets, or issues that surfaced the problem.

How to use it

Run it whenever you're reviewing documentation, onboarding new team members, or just suspicious that an article hasn't kept up with reality. Drop in the article you want to check, and Super delivers a prioritized list of everything that needs attention.

Set it up as a regular review cycle—run it weekly or monthly across your most critical articles to catch drift early. Share the gap analysis with the content owner so they know exactly what to fix and have the sources to back it up. Stop treating documentation review as a guessing game—let your team's own conversations tell you what's out of date.