Starter briefs
One thing has two names; give it one
Name the two terms that mean the same thing, and get the whole codebase moved to one of them.
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
Two different words get used for the same thing across this project, and it's confusing. Pick one of the two names to keep. Find every place the other name is used, in code, in comments, or anywhere it shows on screen, and change it to the one we're keeping. Don't change what anything does, only what it's called.
Why this works
The rule is simple and mechanical: one name replaces another, everywhere. That makes the diff easy to review, since every change should look the same kind of change.
How it runs
Plan, code, review, merge, verify
- plan
Finds every place the retiring name appears, across code, comments, or any user-visible text.
- code
Replaces the retiring name with the kept one site by site, without changing behavior.
- review
Checks every changed site is a pure rename, with no behavior change riding along.
- merge
Opens a pull request limited to the rename named.
- verify
Confirms the retiring name no longer appears anywhere it used to, and nothing else changed.
What you need on hand
- The two names, and which one to keep
- Whether the rename should reach user-visible text or stay internal
- A person to review the diff against that one rule
Done when
- A search for the old name turns up nothing left over
- The kept name is used consistently everywhere the old one was
- Nothing about how the feature behaves changed
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 finds every site an old name still lives at before renaming anything, so the rename lands complete in one change instead of half-done.
Keep going
Related briefs
Pull one duplicated block into one place
Point at the same logic copied into more than one place, and get it merged into one shared version.
Add a field to a form we already have
Name the field, where it should live on an existing form, and get a working save-and-show for it.
Bump one dependency and fix what breaks
Name the dependency and the version, and get an upgrade with whatever it breaks already fixed.
Round up your herd.
Bring every human and every agent onto one table. Watch the work move. Costs update as it happens.