Retire a deprecated component in favour of its replacement
An old component kept alive by a handful of call sites, migrated and deleted.
The ticket
Migrate every call site off a deprecated component and delete it.
Acceptance criteria
- No call site references the old component
- Visual parity is captured at each migrated site
- The old component file is deleted
- Behaviour the replacement lacks is raised rather than quietly dropped
What lands as proof
Per-site captures plus the deletion in the diff, which together prove the migration was complete rather than partial.
Why teams defer it
- The last few call sites are always the awkward ones, which is why they are last.
- Deleting it needs somebody confident nothing else imports it, and that confidence takes a search nobody has run.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: migrate every call site off a deprecated component and delete it. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means old component deleted, visual parity captured per site, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.