doc-maintenance

To detect documentation drift after a major release, audit top-level project files like README.md and doc/SPEC.md against recent commits. This identifies gaps between shipped features and documented specs, enabling timely corrections through minimal, fact-based edits.

Automating a documentation audit using a pull-request workflow involves validating files against a structured checklist and orchestrating a branch + PR workflow. This enforces minimal, fact-based edits guided by an audit checklist and opens a PR with a concise change summary.

Yes, you can audit SPEC and PRODUCT docs for drift during change-dense periods. Applying the audit workflow to top-level documentation during these cycles validates coverage against a structured checklist and proposes necessary factual corrections.

No, the doc-maintenance workflow requires no external dependencies to run. It operates independently to audit project documentation, identify drift between shipped features and descriptions, and orchestrate a branch and PR workflow for corrections.

You should avoid an automated branch-and-PR workflow for documentation updates when changes are not fact-based or minimal. The workflow enforces a structured audit checklist for README, SPEC, and PRODUCT docs, making it unsuitable for unstructured or large-scale rewrites.