3e3d122a4b
- Add design-conformance-reviewer agent for reviewing code against design docs - Add weekly-shipped skill for stakeholder summaries from Jira/GitHub - Fix component counts across marketplace.json, plugin.json, and README - Add worktree constraints to ce-review and resolve_todo_parallel skills - Fix typo in resolve_todo_parallel SKILL.md Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
40 lines
1.9 KiB
Markdown
40 lines
1.9 KiB
Markdown
---
|
||
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/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)
|
||
|
||
**IMPORTANT: Do NOT create worktrees per todo item.** A worktree or branch was already set up before this command was invoked (typically by `/ce:work`). If a worktree path was provided in the original prompt, `cd` into it. Otherwise, find the worktree where the working branch is checked out using `git worktree list`. All agents work in that single checkout — never pass `isolation: "worktree"` when spawning agents.
|
||
|
||
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. Like 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
|