dotagent:doc-review

To catch documentation drift after updating manifest schemas or CLI commands, audit your user-visible code changes to surface stale references and generate a remediation punch list. This prevents outdated guidance from being marked as complete.

Documentation drift occurs when code changes without corresponding user-facing updates. You find moved file paths or renamed plugins by auditing documentation surfaces impacted by user-visible behavior changes to flag exact lines needing updates.

You validate frontmatter presence and fix outdated environment variable references by running a documentation review audit that enforces frontmatter requirements and flags stale references with exact lines for actionable remediation.

Yes, the documentation review process prevents silent passes when auditing plugin protocols by enforcing remediation of stale or moved references before allowing a task to be reported as done, ensuring no outdated guidance slips through.

The best way to audit documentation surfaces impacted by new events or environment variables is to apply a review process across all user-visible changes, returning a punch list of stale references with exact lines and actionable remediation guidance.