release-docs

To update customer-facing documentation for release readiness, scan README, CHANGELOG, FAQs, and plugin.json files to reconcile them with shipped product capabilities. This requires running npm run check-docs as a preliminary validation step.

Documentation accuracy for release readiness is the process of auditing public-facing files like README and CHANGELOG to ensure they match actual shipped product features, preventing customer confusion and discrepancies upon release.

To reconcile the skill roster before a release, run the release-docs skill to scan and update documentation. This ensures the roster and all public-facing documents accurately reflect the latest product changes.

Yes, you need npm to verify README and CHANGELOG accuracy because the documentation audit requires running npm run check-docs as a preliminary step to successfully validate and update files for release readiness.

During a documentation release readiness audit, the system scans README, CHANGELOG, FAQs, and plugin.json files to check for accuracy and update them to match the shipped reality of the product.

Customer-facing documentation becomes outdated before a release when new features and code changes are implemented without immediately updating the README, CHANGELOG, or FAQs, creating discrepancies between the docs and shipped reality.