Find the docs your releases outran.
Every release is a chance for your documentation to quietly fall behind. BuildBetter checks what shipped against what's documented and tells you where the gaps are.
Docs debt, made visible
The question is simple: did the docs keep up with what we shipped?
Reads what you actually shipped
Pulls releases from GitHub, RSS, and your changelog — the same catalog that powers closing the loop. No separate setup to maintain.
Searches your real documentation
Point it at your docs sites and help centers. It finds the pages that should cover each release and shows you the excerpts it matched, so you can judge the call yourself.
Tells you what kind of gap
Missing docs, stale docs, hard to discover, or a UX problem wearing a docs costume. Each one needs a different fix, so each one is named.
Comes with the prompt
Every finding packages the release evidence, the pages checked, and the suggested change into a prompt you can hand to any AI tool and get a draft back.
Shipping is half of it
A feature nobody can find documentation for is a support ticket with a delay on it. Knowledge Gaps runs on the same release catalog that tells customers what shipped, so both halves stay honest.
Built to be triaged
A queue, not an alert storm.
Ranked by urgency
Findings carry urgency and confidence, so the queue tells you what's worth doing rather than just what's different.
Knows customer docs from internal
Mark each source as customer-facing or internal. A backend refactor won't be flagged as a missing customer help page.
Turns into real work
Attach a finding to a project and it stops being a report and starts being something on someone's list.
