Documentation Audit

Assess an existing documentation page. Produces a structured assessment with specific improvement recommendations.

How this differs from docs-reviewer: The docs-reviewer is a voice/style gate for drafts in progress (runs at the end of docs-writer). The docs-audit is an assessment tool for published pages: it checks accuracy against SDK source, identifies content gaps, and optionally compares against competitor docs. Use docs-audit to decide what needs work; use docs-reviewer to verify that a draft is ready to ship.

When to Use

• Before rewriting a doc page (understand current state first)
• When community signals point to confusion around a topic
• During periodic docs health checks
• When comparing Strands docs to competitor docs on the same topic

Inputs

• Target page: File path in site/src/content/docs/ or published URL
• Content type: If known. If not, classify it first.
• Context (optional): Community signals, GitHub issues, or specific concerns