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-2/
Sync Docs After Architecture Decision Update
Problem/Feature Description
The engineering team has been discussing a shift in how internal services communicate. A new Architecture Decision Record has been staged for commit, capturing the decision to adopt GraphQL for service-to-service calls. The author staged the ADR file but hasn't had time to handle the surrounding documentation bookkeeping before handing off to you.
The AGENTS.md at the project root outlines which supporting docs need attention when decision records change. The team wants you to run a doc-sync sweep over the staged changes, apply any needed updates, and produce a summary of what was done.
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 describing:
- What changed paths were detected
- Which docs were checked as a result
- What updates were made (or confirmed clean)
- Any items left unresolved
Do not modify source code files.