Diff-driven doc-staleness sweep. Maps every changed path against the "Doc review — keeping docs true" table in AGENTS.md, runs the load-bearing generated-artifact checks (OpenAPI, AGENTS.md/CLAUDE.md symlinks, ADR index), and patches stale prose docs in the same change. Use when called by `implement-spec` / `review-implementation` at close-out, or when a human says "sync the docs" / "make sure the docs are still true after this change".
90
90%
Does it follow best practices?
Impact
93%
1.32xAverage score across 3 eval scenarios
Passed
No known issues
CLAUDE.md symlink on new AGENTS.md
Git diff used
0%
100%
New AGENTS.md detected
70%
80%
CLAUDE.md symlink check performed
0%
100%
CLAUDE.md symlink created
0%
75%
Symlink target is AGENTS.md
0%
100%
No code files modified
100%
100%
Report produced
100%
100%
Report format — heading
28%
100%
Report symlink action recorded
0%
100%
Prose docs section present
50%
100%
ADR index consistency after new decision record
Git diff used
100%
85%
AGENTS.md table consulted
100%
100%
ADR index row added
100%
100%
ADR 004 row status correct
100%
100%
Superseded ADR checked
100%
100%
No code files modified
100%
100%
Report produced
100%
100%
Report heading format
28%
28%
Report — generated artifacts section
62%
75%
Report — prose docs section
57%
71%
Unimplicated docs untouched
100%
100%
CHANGELOG verification for user-facing feature
Git diff used
71%
42%
AGENTS.md table consulted
100%
100%
CHANGELOG checked
100%
100%
CHANGELOG entry added
100%
100%
Correct CHANGELOG section
100%
100%
docs/features.md checked
100%
100%
docs/internals.md untouched
100%
100%
No code files modified
100%
100%
Report produced
100%
100%
Report heading format
20%
100%
Report — generated artifacts section
100%
100%