home / skills / everyinc / compound-engineering-plugin / resolve_todo_parallel

resolve_todo_parallel skill

safe

/plugins/compound-engineering/skills/resolve_todo_parallel

This skill resolves all unresolved TODOs in parallel using a structured plan and mermaid diagram to optimize workflow.

npx playbooks add skill everyinc/compound-engineering-plugin --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
argument-hint: "[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/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 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 resolves all pending CLI TODOs using parallel processing to speed up codebase cleanup. It analyzes TODO entries, plans dependency-aware execution, and then spawns parallel resolver agents to implement and commit fixes. It is tailored for compound engineering workflows and respects intentional pipeline artifacts.

How this skill works

The skill scans the /todos/*.md directory to collect unresolved TODO items. It filters out any TODOs that recommend deleting or ignoring files in docs/brainstorms, docs/plans, or docs/solutions and marks those as wont_fix. It produces a dependency-aware Todo list and a mermaid flow diagram showing which items can run in parallel and which must run sequentially, then spawns a pr-comment-resolver agent for each remaining TODO and runs them in parallel before committing changes and removing the TODO entries.

When to use it

When you have multiple CLI TODOs that can be resolved simultaneously to shorten turnaround time.
When TODO resolution may have inter-item dependencies that need planning before execution.
When you want automated PR-style comment resolution with per-TODO subagents.
When respecting permanent pipeline artifacts in docs is required.
Before bulk commits to ensure safe parallel edits and proper sequencing.

Best practices

Run the analysis step first to detect dependency chains and mark pipeline-artifact TODOs wont_fix.
Always generate a mermaid flow diagram to visualize parallelizable work and sequencing constraints.
Limit parallelism to resource constraints of the CI or development environment to avoid conflicts.
Ensure each pr-comment-resolver runs in an isolated workspace to prevent race conditions.
Verify changes locally or via CI before committing and pushing to remote.

Example use cases

A repository with dozens of small CLI TODOs that can be handled by separate agents concurrently.
A code cleanup sprint where some TODOs rename identifiers and others update docs, requiring dependency planning.
Automating PR comment resolutions raised by code review bots across many files.
A compound-engineering pipeline where docs/brainstorms or docs/plans must remain untouched and flagged.

FAQ

What happens to TODOs that touch the specified docs directories?

Any TODO recommending deleting, removing, or gitignoring files in docs/brainstorms, docs/plans, or docs/solutions is skipped and marked wont_fix.

Can all TODOs always be resolved in parallel?

Not always. The skill builds a dependency-aware plan and shows a mermaid diagram to indicate which items must run first and which can run concurrently.