doc-maintenance

To detect documentation drift, audit top-level files like README.md and SPEC.md against recent git history. This identifies shipped features missing from docs or outdated upcoming features, proposing minimal edits to resolve inconsistencies.

The best way to update README and SPEC files after a major feature merge is to run an audit that enforces a minimal-patch workflow, creates a dedicated branch, and opens a pull request with the proposed documentation edits.

Yes, you can automatically create a branch and open a PR for documentation updates. The workflow scaffolds the branch, applies minimal patches to README.md, doc/SPEC.md, and doc/PRODUCT.md, and submits the pull request.

A minimal-patch workflow for documentation audits works by comparing top-level docs against git history and proposing only the smallest necessary edits to fix drift. It updates the review cursor and reports findings before opening a PR.

You do not need to manually review changes before the PR is opened because the workflow proposes minimal edits and reports its findings automatically. However, reviewing the generated pull request ensures the documentation updates align with your project context.