Docs Audit

Documentation-experience audit and debugging for any surface someone reads to learn, integrate, recover, or retrieve — developer docs, end-user help, and agent-readable docs. Provenance lives in skill.json; this file is runtime routing only.

Produces: an intent-specific report — audit-report.md (friction findings, score, audience conflicts) or debug-runbook.md (ranked hypotheses, fix path, prevention).

Core principle

Match the page to the audience's job and keep it true. If a competent reader has to guess the page type, hunt for the canonical fact, copy a stale example, or fight prose that fits no audience, that is a docs problem worth a finding.

Activation