Lesson 57 · Understand your customers
Find the docs your releases broke
Gaps, filters, a gap's evidence, and the four-step setup.
You’ll be able to
- See which docs your releases left behind
- Read the evidence and hand off the fix
- Set up Knowledge Gaps in four steps
Read the docs
Synced from docs.buildbetter.aiThe help pages for this lesson, kept up to date. Read them here without leaving the lesson.
Transcript
Knowledge Gaps reads every release you ship against your docs, and tells you which pages are missing or out of date.
Open Knowledge, then Knowledge Gaps. Each card is one release, with its urgency, how well your docs match, and what to do next.
Filter by status, urgency, or gap type, like missing docs or stale docs.
Click a card to see why it's here, the evidence from the release, the docs it checked, and a suggested update.
Approve it, assign it, or attach it to a project. Copy prompt hands the fix to a coding agent.
Check for documentation gaps analyzes new releases. It shows the credit cost before anything runs.
Setup takes four steps. First, pick where your releases are written down, like the BuildBetter changelog, GitHub releases, or a changelog page.
Connect it, and point at your documentation. Last, analyze one release to see a real result. The cost shows before you run it.
Next up, Search.
