CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.32x
Quality

90%

Does it follow best practices?

Impact

93%

1.32x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-1/

Finalize the Payments Package Addition

Problem/Feature Description

A developer on the platform team has scaffolded a new packages/payments sub-package in the monorepo. The package includes its own AGENTS.md file that maps source paths to docs. The changes are staged and ready to review.

Before this work gets merged, the team lead wants a doc-sync pass to ensure the new package follows all project conventions and that no documentation is left in an inconsistent state. The root AGENTS.md at the repo root explains the project's doc-review conventions — you should use it as your guide for what to check.

The repository is located in the current working directory (inputs/). Run your work from there.

Output Specification

Produce a file called doc-sync-report.md in the current working directory summarizing what was checked and what actions were taken. The report should make clear which files were verified, which actions were performed, and any remaining issues.

Do not modify any source code files — only documentation and necessary structural files.

SKILL.md

tile.json