todo-resolve

name	todo-resolve
description	Use when batch-resolving approved todos, especially after code review or triage sessions
argument-hint	[optional: specific todo ID or pattern]

Resolve approved todos using parallel processing, document lessons learned, then clean up.

Only ready todos are resolved. pending todos are skipped — they haven't been triaged yet. If pending todos exist, list them at the end so the user knows what was left behind.

Workflow

1. Analyze

Scan .context/agent-workflows/todos/*.md and legacy todos/*.md. Partition by status:

• ready (status field or -ready- in filename): resolve these.
• pending: skip. Report them at the end.
• complete: ignore, already done.

If a specific todo ID or pattern was passed as an argument, filter to matching todos only (still must be ready).

Residual actionable work from code-review autofix pass after its safe_auto pass will already be ready.

Skip any todo that recommends deleting, removing, or gitignoring files in docs/brainstorms/, docs/plans/, or docs/solutions/ — these are intentional pipeline artifacts.

2. Plan

Create a task list grouped by type (e.g., TaskCreate in Claude Code, update_plan in Codex). Analyze dependencies -- items that others depend on run first. Output a mermaid diagram showing execution order and parallelism.

3. Implement (PARALLEL)

Spawn a general-purpose agent per item. Prefer parallel; fall back to sequential respecting dependency order.

Batching: 1-4 items: direct parallel returns. 5+ items: batches of 4, each returning only a short status summary (todo handled, files changed, tests run/skipped, blockers).

For large sets, use a scratch directory at .context/agent-workflows/todo-resolve/<run-id>/ for per-resolver artifacts. Return only completion summaries to parent.

4. Commit & Resolve

Commit changes, mark todos resolved, push to remote.

GATE: STOP. Verify todos resolved and changes committed before proceeding.

5. Capture Lessons Learned

Document any reusable lesson that surfaced during the todo resolution. Todo resolutions often expose patterns and architectural insights worth capturing.

GATE: STOP. Verify a solution document exists in docs/solutions/ if there were durable lessons. If none (user declined or no learnings), continue.

6. Clean Up

Delete completed/resolved todo files from both paths. If a scratch directory was created at .context/agent-workflows/todo-resolve/<run-id>/, delete it (unless user asked to inspect).

Todos resolved: [count]
Pending (skipped): [count, or "none"]
Lessons documented: [path to solution doc, or "skipped"]
Todos cleaned up: [count deleted]

If pending todos were skipped, list them:

Skipped pending todos (run /todo-triage to approve):
  - 003-pending-p2-missing-index.md
  - 005-pending-p3-rename-variable.md