cross-repo-todo-triagelisted

# Cross-Repo TODO Triage ## Overview Technique for discovering, consolidating, and investigating TODO items across a multi-repo codebase using parallel exploration agents to verify completion status without building or running code. ## When to Use - Periodic backlog grooming across a monorepo - Before planning when TODOs are scattered across repos - When worktrees may have divergent TODO state - When suspecting items may already be fixed but not removed ## Core Pattern ### Phase 1: Discovery Parallel `Glob` for `**/TODO.md` and `**/TODO`. Skip vendored/upstream files. ### Phase 2: Read and Deduplicate Read all TODO files in parallel. For worktrees, compare against canonical (master branch) copy -- worktrees may be stale or have unique items not yet merged. ### Phase 3: Consolidate and Prioritize Merge all unique open items into a single list. Group by: | Priority | Criteria | | -------- | ----------------------------------------- | | P0 | Data loss, crashes, security | | P1 | Broken tests, build failures | | P2 | Small targeted improvements (1-file fixes) | | P3 | Test infrastructure, migration | | P4+ | Feature work, documentation debt, exploration | ### Phase 4: Parallel Completion Investigation Fan out 4-8 Explore agents, each with a thematically coherent subset of items. Each agent: 1. Reads the specific source files referenced by the TODO 2. Checks recent git