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

refactor(skills): migrate commands to skills directory structure

Browse Source 
Move all 27 command .md files from commands/ to skills/*/SKILL.md
format. Claude Code 2.1.3+ merged commands and skills - both create
slash commands and work identically. Skills add optional features
like supporting files and automatic context loading.

- commands/ce/*.md -> skills/ce-*/SKILL.md
- commands/workflows/*.md -> skills/workflows-*/SKILL.md
- commands/*.md -> skills/*/SKILL.md
- Update plugin.json and marketplace.json descriptions
- Update CLAUDE.md directory structure docs
- Update deploy-docs and generate_command references

Fixes #116

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Matt Van Horn
2026-03-08 21:48:29 -07:00
committed by Matt Van Horn
parent e426799f85
commit 3e99c11c0b
30 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
plugins/compound-engineering/commands/resolve_todo_parallel.md
View File

@@ -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/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