Complete one entry from the tech debt list
One item from the list, done exactly as the person who understood it wrote it down.
The ticket
Resolve one debt-register entry as written.
Acceptance criteria
- The work matches what the entry describes
- The register entry is closed and links to the pull request
- Scope changes from the original entry are stated rather than absorbed
- Anything discovered along the way is filed as a new entry
What lands as proof
A closed register entry linked to the change that closed it, so the register stays a live document.
Why teams defer it
- The register is written by people with context and read by people without it, so entries age into puzzles.
- Nothing enforces the register, so entries accumulate faster than they close.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: resolve one debt-register entry as written. 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 the register entry is closed by the pull request that did it, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.