update-knowledge-base

To keep help center documentation in sync, you can cross-reference recently shipped tickets against your changelog to surface outdated articles and generate updated draft copy for missing coverage directly to your docs repository.

Finding undocumented features after a release involves cross-referencing shipped tickets with your existing help center and changelog to detect documentation gaps and identify product areas that lack adequate coverage.

Generating draft copy for outdated knowledge-base articles is done by cross-referencing shipped tickets with current documentation to identify stale content and output ready-to-publish updates to your docs repository.

Yes, you can detect documentation debt across product areas by cross-referencing shipped tickets with the help center and changelog on a configured cadence to surface outdated articles and missing coverage.

Yes, integrating a ticket source is a functional requirement to identify outdated changelog entries, as the skill cross-references recently shipped tickets against your changelog and help center URLs to surface documentation gaps.

A documentation gap analysis should be run on a configured cadence or after each release, cross-referencing shipped tickets with the help center and changelog to continuously surface outdated articles and undocumented features.