qa-docs-coverage

# QA Docs Coverage (Jan 2026) - Discovery, Freshness, and Runbook Quality ## Modern Best Practices (January 2026) - **Docs as QA**: Treat docs as production artifacts with owners, review cadence, and CI quality gates (links/style/contracts/freshness) - **Contract-first**: Validate OpenAPI/AsyncAPI/JSON Schema in CI; use coverage tools (Swagger Coverage / OpenAPI Coverage) to detect gaps - **Runbook testability**: Every runbook must be executable in staging; validate with synthetic tests and incident exercises - **Automation + observability**: Track coverage %, freshness, and drift via CI dashboards; prevent regressions via PR checklists This skill provides operational workflows for auditing existing codebases, identifying documentation gaps, and systematically generating missing documentation. It complements [docs-codebase](../docs-codebase/SKILL.md) by providing the **discovery and analysis** layer. **Key Principle**: Templates exist in docs-codebase. This skill tells you **what** to document and **how to find** undocumented components. Core references: [Diataxis](https://diataxis.fr/) (doc structure), [OpenAPI](https://spec.openapis.org/oas/latest.html) (REST), [AsyncAPI](https://www.asyncapi.com/) (events). ## When to use - Auditing an existing repo for missing/outdated documentation - Adding documentation quality gates (lint/link checks/contracts/freshness) to CI/CD - Validating runbooks for incident readiness (MTTR reduction) ## When to avoid - Writing new docum...