Implement the reminders left in one module
Comment reminders turned into the working code their authors described, rather than deleted.
The ticket
Implement the outstanding work described by reminder comments in one module.
Acceptance criteria
- Each reminder becomes working code with a test
- The comment is removed only once its work is done
- Reminders that are no longer wanted are removed with a reason
- Nothing is deferred to a new reminder
What lands as proof
A test per implemented reminder, so the comment is removed because the work exists, not because it was tidied.
Why teams defer it
- The author knew what they meant and wrote three words about it.
- Some reminders describe work that is now wrong, so each one needs a judgement before any code.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: implement the outstanding work described by reminder comments in one module. 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 each one becomes working code with a test, not a deletion, 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.