Code
Ship a feature
Implement a change across every file it actually touches.
Fill it in
Describe the change and its edges.
Where to make the change.
Cover the new behaviour before delivering.
Your prompt
Build this in [your repository]: [your what to build] Find every place it touches before changing any of them. The reason a change like this goes wrong is never the obvious file: it is the email template, the export path, the one component that reimplemented the thing locally. Search for the pattern, not just the name. Work in one pass so the codebase is never half-migrated, and keep the change mechanical where it can be. A reviewer should be able to read the diff and see one idea applied consistently rather than a series of unrelated decisions. Add tests for the new behaviour, and specifically for the edge you found while searching that nobody would have thought of up front.
Use Ship a featureOpens with everything above already filled in.
Why this works
A feature shipped across a codebase leaves the two places nobody remembered. This finds every site rather than the obvious ones, and adds the tests that prove it.