matthew-a-carr/sync-docs
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
task.mdevals/scenario-3/
Wrap Up the Bulk Delete Feature
Problem/Feature Description
A developer has finished implementing a bulk-delete capability for the product's list views. The implementation is in src/features/ and the feature documentation has been updated. The changes are staged and ready to commit.
Before closing out this feature branch, the team wants a final documentation check to make sure everything is consistent. The project's AGENTS.md defines which docs need attention based on which source paths were touched. You should use it to guide your sweep.
The repository is in the current working directory (inputs/). Run all commands from there.
Output Specification
Produce a file called doc-sync-report.md in the current working directory. It should cover:
- How many paths changed
- The result of each doc check the AGENTS.md table triggered
- Any edits made and what specifically was changed
- Anything left unresolved
Do not modify any source code files.