resolve_todo_parallel
SkillProductivityResolve all pending CLI todos using parallel processing
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the resolve_todo_parallel skill
What this skill tells your AI
The instructions your AI receives, as published by ratacat/claude-skills in skills/resolve_todo_parallel/SKILL.md and read by ahel’s review.
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
- Task pr-comment-resolver(comment1)
- Task pr-comment-resolver(comment2)
- 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
Signals
- GitHub stars
- 53
- Forks
- 9
- Last commit
- Feb 2026
Advanced
- Catalog kind
- skill
- Gateway key
resolve-todo-parallel- Source
- github.com/ratacat/claude-skills