References a plan invalidates are cleaned up in the same sprint
acceptednot accepted
When a plan deletes or renames something others reference, the cleanup is a milestone task of the same sprint with its own DoD, never a follow-up sweep.
On this page
- Author
- agent
- Created
- Updated
- Review
- not shown
- targets
- groom/draft-plan
- brief
- When the plan deletes or renames partials, agents, CLAUDE.md lines or doc links, make the cleanup of every stale reference a milestone task with its own DoD in this sprint.
Rule§
When a plan's work invalidates references — a deleted partial, a renamed agent, a
status line in CLAUDE.md, a broken doc link — cleaning them up is a milestone
task inside the same sprint, with its own DoD. A half-stale working tree at sprint
close is itself the documentation gap; a "sweep it up after" follow-up leaves the
repo inconsistent and gets dropped.
Follows from§
- Single source — a stale reference is a second, wrong copy of a fact. In the retro on migrating the retro skill to the template pipeline, deleting a partial and updating a CLAUDE.md status block as their own milestone landed both inside the sprint.