resolve-todo-parallel

Resolve all TODO comments using parallel processing, document lessons learned, then clean up completed todos.

Workflow

1. Analyze

Get all unresolved TODOs from the /todos/*.md directory

If any todo recommends deleting, removing, or gitignoring files in docs/brainstorms/, docs/plans/, or docs/solutions/, skip it and mark it as wont_fix. These are compound-engineering pipeline artifacts that are intentional and permanent.

2. Plan

Create a task list of all unresolved items grouped by type (e.g., TaskCreate in Claude Code, update_plan in Codex). Analyze dependencies and prioritize items that others depend on. For example, if a rename is needed, it must complete before dependent items. Output a mermaid flow diagram showing execution order — what can run in parallel, and what must run first.

3. Implement (PARALLEL)

Spawn a compound-engineering:workflow:pr-comment-resolver agent for each unresolved item.

If there are 3 items, spawn 3 agents — one per item. Prefer running all agents in parallel; if the platform does not support parallel dispatch, run them sequentially respecting the dependency order from step 2.