john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

feat: make skills platform-agnostic across coding agents (#330)

Browse Source
This commit is contained in:
Trevin Chow
2026-03-21 17:35:22 -07:00
committed by GitHub
parent cfbfb6710a
commit 52df90a166
9 changed files with 215 additions and 580 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -16,19 +16,13 @@ If any todo recommends deleting, removing, or gitignoring files in `docs/brainst
### 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.
Create a task list of all unresolved items grouped by type (e.g., `TaskCreate` in Claude Code, `update_plan` in Codex). Analyze dependencies and prioritize items that others depend on. For example, if a rename is needed, it must complete before dependent items. Output a mermaid flow diagram showing execution order — what can run in parallel, and what must run first.
### 3. Implement (PARALLEL)
Spawn a pr-comment-resolver agent for each unresolved item in parallel.
Spawn a `compound-engineering:workflow:pr-comment-resolver` agent for each unresolved item.
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.
If there are 3 items, spawn 3 agents — one per item. Prefer running all agents in parallel; if the platform does not support parallel dispatch, run them sequentially respecting the dependency order from step 2.
### 4. Commit & Resolve
@@ -40,7 +34,7 @@ GATE: STOP. Verify that todos have been resolved and changes committed. Do NOT p
### 5. Compound on Lessons Learned
Run the `ce:compound` skill to document what was learned from resolving the todos.
Load 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.