feat: edit resolve_todos_parallel skill for complete todo lifecycle (#292)

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

plugins/compound-engineering/README.md

@@ -100,7 +100,7 @@ Core workflow commands use `ce:` prefix to unambiguously identify them as compou
 | `/reproduce-bug` | Reproduce bugs using logs and console |
 | `/resolve_parallel` | Resolve TODO comments in parallel |
 | `/resolve_pr_parallel` | Resolve PR comments in parallel |
-| `/resolve_todo_parallel` | Resolve todos in parallel |
+| `/resolve-todo-parallel` | Resolve todos in parallel |
 | `/triage` | Triage and prioritize issues |
 | `/test-browser` | Run browser tests on PR-affected pages |
 | `/xcode-test` | Build and test iOS apps on simulator |

plugins/compound-engineering/skills/ce-review/SKILL.md

@@ -439,7 +439,7 @@ After creating all todo files, present comprehensive summary:
 3. **Work on Approved Todos**:
 
    ```bash
-   /resolve_todo_parallel  # Fix all approved items efficiently
+   /resolve-todo-parallel  # Fix all approved items efficiently
    ```
 
 4. **Track Progress**:

plugins/compound-engineering/skills/file-todos/SKILL.md

@@ -187,7 +187,7 @@ Work logs serve as:
 |---------|------|------|
 | Code review | `/ce:review` → Findings → `/triage` → Todos | Review agent + skill |
 | PR comments | `/resolve_pr_parallel` → Individual fixes → Todos | gh CLI + skill |
-| Code TODOs | `/resolve_todo_parallel` → Fixes + Complex todos | Agent + skill |
+| Code TODOs | `/resolve-todo-parallel` → Fixes + Complex todos | Agent + skill |
 | Planning | Brainstorm → Create todo → Work → Complete | Skill |
 | Feedback | Discussion → Create todo → Triage → Work | Skill + slash |
 

plugins/compound-engineering/skills/lfg/SKILL.md

@@ -25,7 +25,7 @@ CRITICAL: You MUST execute every step below IN ORDER. Do NOT skip any required s
 
 5. `/ce:review`
 
-6. `/compound-engineering:resolve_todo_parallel`
+6. `/compound-engineering:resolve-todo-parallel`
 
 7. `/compound-engineering:test-browser`
 

plugins/compound-engineering/skills/resolve-todo-parallel/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: resolve-todo-parallel
+description: Resolve all pending CLI todos using parallel processing, compound on lessons learned, then clean up completed todos.
+argument-hint: "[optional: specific todo ID or pattern]"
+---
+
+Resolve all TODO comments using parallel processing, document lessons learned, then clean up completed todos.
+
+## 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. 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
+
+GATE: STOP. Verify that todos have been resolved and changes committed. Do NOT proceed to step 5 if no todos were resolved.
+
+### 5. Compound on Lessons Learned
+
+Run the `ce:compound` skill to document what was learned from resolving the todos.
+
+The todo resolutions often surface patterns, recurring issues, or architectural insights worth capturing. This step ensures that knowledge compounds rather than being lost.
+
+GATE: STOP. Verify that the compound skill produced a solution document in `docs/solutions/`. If no document was created (user declined or no non-trivial learnings), continue to step 6.
+
+### 6. Clean Up Completed Todos
+
+List all todos and identify those with `done` or `resolved` status, then delete them to keep the todo list clean and actionable.
+
+After cleanup, output a summary:
+
+```
+Todos resolved: [count]
+Lessons documented: [path to solution doc, or "skipped"]
+Todos cleaned up: [count deleted]
+```

plugins/compound-engineering/skills/resolve_todo_parallel/SKILL.md

@@ -1,37 +0,0 @@
----
-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

plugins/compound-engineering/skills/slfg/SKILL.md

@@ -28,7 +28,7 @@ Wait for both to complete before continuing.
 
 ## Finalize Phase
 
-7. `/compound-engineering:resolve_todo_parallel` — resolve any findings from the review
+7. `/compound-engineering:resolve-todo-parallel` — resolve findings, compound on learnings, clean up completed todos
 8. `/compound-engineering:feature-video` — record the final walkthrough and add to PR
 9. Output `<promise>DONE</promise>` when video is in PR
 

plugins/compound-engineering/skills/triage/SKILL.md

@@ -204,7 +204,7 @@ During triage, the following status updates occurred:
 2. Start work on approved items:
 
    ```bash
-   /resolve_todo_parallel  # Work on multiple approved items efficiently
+   /resolve-todo-parallel  # Work on multiple approved items efficiently
    ```
 
 3. Or pick individual items to work on
@@ -297,7 +297,7 @@ Progress: 3/10 completed | Estimated time: ~2 minutes remaining
 - ✅ Update todo files (rename, frontmatter, work log)
 - ❌ Do NOT implement fixes or write code
 - ❌ Do NOT add detailed implementation details
-- ❌ That's for /resolve_todo_parallel phase
+- ❌ That's for /resolve-todo-parallel phase
 ```
 
 When done give these options
@@ -305,7 +305,7 @@ When done give these options
 ```markdown
 What would you like to do next?
 
-1. run /resolve_todo_parallel to resolve the todos
+1. run /resolve-todo-parallel to resolve the todos
 2. commit the todos
 3. nothing, go chill
 ```