# One doc page no longer matches the product

One doc page no longer matches the product: Point at the doc page and the feature it describes, and get the drifted parts corrected.

Source: https://codeherder.com/starter-briefs/doc-page-out-of-date/

Starter briefs

Point at the doc page and the feature it describes, and get the drifted parts corrected.

[Request access →](https://codeherder.com/get-started/#request-access) [Part of: Keep the docs true →](https://codeherder.com/use-cases/keep-the-docs-true/)

## The brief

Copy this text as it is, or change the specifics to match your own case, then file it as a task.

Copy this and file it as a task

Copy brief

```
This doc page describes how a feature works, but the feature has changed since it was written and some of the steps no longer match what actually happens. Go through the page, check each step against how the product behaves today, and correct anything that has drifted. Leave the parts that are still correct as they are.
```

## Why this works

It points at one page and one feature to check it against, so the scope stays small: read, compare, correct. A reviewer can check the same page against the same feature and confirm the correction, without reading a wider set of docs.

How it runs

## Plan, code, review, merge, verify

1. plan Reads the doc page and the feature it describes, and lists every step or claim that needs checking against current behavior.
2. code Corrects each step that no longer matches, and leaves the rest of the page untouched.
3. review Re-checks every correction against how the feature behaves today, ignoring the doc's old wording.
4. merge Opens a pull request limited to the one page named.
5. verify Confirms every step on the page now matches what the feature actually does.

## What you need on hand

- The doc page that might be stale
- Access to the feature it describes, so its current behavior can be checked directly
- A person to confirm each correction before it ships

## Done when

- Every step on the page matches current behavior when you try it
- Nothing that was already correct was rewritten unnecessarily
- The page reads as one coherent set of instructions, not a patchwork

## Proof, not a promise

No real task in examples.ts matches this brief's exact shape yet. What's real is the mechanism: an agent checks a doc page's own claims against the feature it describes, corrects only what has drifted, and a person confirms each correction before it merges.

Keep going

## Related briefs

[A control that is cut off on a phone File the button or menu that gets clipped on a narrow screen, and get it fixed.](https://codeherder.com/starter-briefs/control-cut-off-on-phone/) [Add a missing test for a bug that shipped Name the bug that already got fixed, and get a test that makes sure it can't come back unnoticed.](https://codeherder.com/starter-briefs/test-for-a-shipped-bug/) [Cover the one file nobody has tests for Name a file with no test coverage, and get a real test suite for what it actually does.](https://codeherder.com/starter-briefs/cover-the-untested-file/)

[← See every brief](https://codeherder.com/starter-briefs)