From atv-starter-kit
Resolves all pending CLI TODOs from /todos/*.md using parallel pr-comment-resolver agents, dependency-aware Mermaid planning, commits changes, and marks resolved.
How this skill is triggered — by the user, by Claude, or both
Slash command
/atv-starter-kit:resolve_todo_parallelThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
[optional: specific todo ID or pattern]
[optional: specific todo ID or pattern]
Resolve all TODO comments using parallel processing.
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.
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.
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
Always run all in parallel subagents/Tasks for each Todo item.
npx claudepluginhub all-the-vibes/atv-starterkit --plugin atv-starter-kitBatch-resolves approved 'ready' todos: scans directories, plans parallel execution with dependencies, commits changes, documents lessons learned, cleans up files. Reports skipped pendings.
Picks the next executable task from project-root TODO.md by priority and dependency, marks it in-progress, and executes it. Uses a structured task format with priority, ID, and dep fields.
Manage file-based todos in todos/ directory. Use when creating, triaging, or tracking todos and integrating them with code review.