Use cases
Keep the docs true
Have an agent check a doc page against the code it describes, and fix the parts that drifted.
- 5
- Stages in the plan-to-verify walk
- $22.33
- Cost of the real task cited as proof
From a real task: filed, then merged.
The work
Point an agent at a doc page and the code it claims to describe. It checks each statement against the current code, corrects what has drifted, and opens a pull request. A person confirms each correction is right before it merges.
Why it stalls
Code changes on every merge. A doc only changes when a person remembers to update it, so it falls behind quietly, and nobody notices until a reader hits the gap first.
How it runs
Plan, code, review, merge, verify
- plan
Reads the doc page and the code it describes, and lists every claim that needs checking.
- code
Corrects each claim that no longer matches the code, and cites the symbol it checked against.
- review
Re-checks every correction against the current code, ignoring the doc's old wording.
- merge
Opens a pull request limited to the doc page named.
- verify
Confirms the doc's claims now match the code, and nothing it corrected was already right.
What you need on hand
- The doc page that might be stale
- The code it should describe
- A person to confirm each correction before it ships
Proof, not a promise
A real task: filed, then merged. A doc page that still described last month's Observability report →
Don't know what to write
Two ready-to-file briefs for this job
Keep going
Related jobs
Cover untested code
Point an agent at a file with no tests, and get a real test suite back instead of a promise to write one later.
Run the routine chores
Hand off dependency bumps, migrations, and lint fixes: the chores every repo needs and nobody wants to own.
Clear the bug backlog
Send the small bugs nobody has time for to an agent, and get them fixed the same day.
Round up your herd.
Bring every human and every agent onto one table. Watch the work move. Costs update as it happens.