playbooks

home / skills / ratacat / claude-skills / resolve_todo_parallel

resolve_todo_parallel skill

/skills/resolve_todo_parallel

This skill resolves all pending CLI TODOs in parallel, analyzes dependencies, and generates a plan to execute items efficiently.

npx playbooks add skill ratacat/claude-skills --skill resolve_todo_parallel

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.5 KB
---
name: resolve_todo_parallel
description: Resolve all pending CLI todos using parallel processing
---

## Arguments
[optional: specific todo ID or pattern]

Resolve all TODO comments using parallel processing.

## Workflow

### 1. Analyze

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

If any todo recommends deleting, removing, or gitignoring files in `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 TodoWrite list of all unresolved items grouped by type.Make sure to look at dependencies that might occur and prioritize the ones needed by others. For example, if you need to change a name, you must wait to do the others. Output a mermaid flow diagram showing how we can do this. Can we do everything in parallel? Do we need to do one first that leads to others in parallel? I'll put the to-dos in the mermaid diagram flow‑wise so the agent knows how to proceed in order.

### 3. Implement (PARALLEL)

Spawn a pr-comment-resolver agent for each unresolved item in parallel.

So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. liek this

1. Task pr-comment-resolver(comment1)
2. Task pr-comment-resolver(comment2)
3. Task pr-comment-resolver(comment3)

Always run all in parallel subagents/Tasks for each Todo item.

### 4. Commit & Resolve

- Commit changes
- Remove the TODO from the file, and mark it as resolved.
- Push to remote

Overview

This skill automates resolution of pending CLI TODOs by detecting, planning, and resolving items with parallel subagents. It scans a repository's /todos/*.md files, creates a dependency-aware plan, and launches parallel workers to implement and commit fixes. The skill enforces safety rules to skip intentional pipeline artifacts and marks them as wont_fix.

How this skill works

The skill scans /todos/*.md to collect unresolved TODO entries and filters out any that recommend deleting or ignoring files under docs/plans/ or docs/solutions/ (those are marked wont_fix). It produces a TodoWrite list grouped by type, analyzes dependencies, and outputs a mermaid flow diagram to indicate which tasks can run concurrently and which must run in sequence. For each resolvable TODO it spawns a pr-comment-resolver task in parallel, commits changes, removes the TODO marker, and pushes the branch.

When to use it

  • You have multiple independent TODOs across /todos/*.md and want faster resolution.
  • You need to run fixes in parallel but still respect inter-TODO dependencies.
  • You want an automated, auditable process that commits and removes TODOs.
  • You must avoid touching intentional pipeline artifacts in docs/plans or docs/solutions.

Best practices

  • Keep TODO entries focused and actionable so pr-comment-resolver agents can implement them automatically.
  • Tag or structure TODO metadata (IDs, types, dependencies) to improve automatic grouping and prioritization.
  • Review the generated mermaid flow diagram before execution to confirm dependency assumptions.
  • Limit parallelism when TODOs change shared files to avoid merge conflicts; prefer sequence in that case.
  • Use CI checks after pushes to validate changes made by subagents.

Example use cases

  • Resolve linting or formatting TODOs spread across multiple docs simultaneously.
  • Apply small refactors (rename variables, update comments) that are independent and safe to parallelize.
  • Batch-fix documentation typos and remove corresponding TODO markers.
  • Automate removal of obsolete scaffolding notes while preserving pipeline artifacts by skipping docs/plans and docs/solutions entries.

FAQ

What happens if a TODO touches the same file as another TODO?

The planner detects file-level dependencies and sequences those tasks rather than running them concurrently to avoid conflicts.

How are pipeline-artifact TODOs handled?

Any TODO recommending deletion, removal, or gitignore of files in docs/plans/ or docs/solutions/ is skipped and marked wont_fix.