Documentation Drift Review
Own change-scoped documentation accuracy through separate inspection and repair stages.
Workflow
- Confirm the changed behavior and whether the task authorizes documentation edits or only a read-only drift report.
- Identify canonical, generated, mirrored, and external documentation describing the changed surface.
- Compare implementation with README files, instructions, APIs, schemas, operational docs, examples, templates, and command help in scope.
- Report concrete drift with the affected claim, implementation evidence, canonical owner, and required correction.
- When edits are authorized, update only directly affected canonical documents in their existing style.
- Change generated documentation or help at its source and regenerate it through the repository's established command.
- For authorized prose edits, use
text-improve on the final changed text without expanding the drift scope.
Use docs-review for broader documentation quality, repo-context-document for deliberate docs/context/ work, plan-update for plan mechanics, and spec-update for semantic contract decisions.
Do not restructure documentation, hand-edit generated content, change product behavior, or modify external documentation without authority.
Finish with changed documents, an evidenced no-change result, or unresolved owner decisions.
1---2name: docs-drift-review3description: Review documentation for drift caused by the current code or configuration change. Use to identify concrete inaccuracies and, when authorized, repair only directly affected documentation.4---56# Documentation Drift Review78Own change-scoped documentation accuracy through separate inspection and repair stages.910## Workflow11121. Confirm the changed behavior and whether the task authorizes documentation edits or only a read-only drift report.132. Identify canonical, generated, mirrored, and external documentation describing the changed surface.143. Compare implementation with README files, instructions, APIs, schemas, operational docs, examples, templates, and command help in scope.154. Report concrete drift with the affected claim, implementation evidence, canonical owner, and required correction.165. When edits are authorized, update only directly affected canonical documents in their existing style.176. Change generated documentation or help at its source and regenerate it through the repository's established command.187. For authorized prose edits, use `text-improve` on the final changed text without expanding the drift scope.1920Use `docs-review` for broader documentation quality, `repo-context-document` for deliberate `docs/context/` work, `plan-update` for plan mechanics, and `spec-update` for semantic contract decisions.2122Do not restructure documentation, hand-edit generated content, change product behavior, or modify external documentation without authority.2324Finish with changed documents, an evidenced no-change result, or unresolved owner decisions.
yarlson