Even better: do it now, or not at all. If it is a failing test do it now anyway. The reason is the person adding the TODO may have a bias that their thing rea

Even better: do it now, or not at all. If it is a failing test do it now anyway. The reason is the person adding the TODO may have a bias that their thing really is the most important tech debt. However I would step back and figure out what tech debt payback offers the best ROI with the team. If you have a pet hate refactor you want done, add it to a personal list and bring it up for consideration in that process. Or just fix it as part of your task if practical to do so.