the-rabak/resolve_todo_parallel
.github/skills/resolve_todo_parallel/SKILL.md
Resolve all pending CLI todos using parallel processing
$ install --global
skillsauthnpx skillsauth add the-rabak/compound-engineering-plugin resolve_todo_parallelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 11, 2026, 8:39 PM20.9s1 file scanned
SKILL.md
- name:
- resolve_todo_parallel
- description:
- Resolve all pending CLI todos using parallel processing
Arguments
[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
- Task pr-comment-resolver(comment1)
- Task pr-comment-resolver(comment2)
- 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
Related Skills
the-rabak/focused-ticket-priming
tools
VerifiedTrustedCommunity
Package one plan execution packet into a compact ticket-local execution packet with parent refs, scope fences, feature-home ownership, and evidence commands. Use when converting plans into local tickets or when execution needs one ticket-sized context pack without the full plan.
1SKILL.mdUpdated May 22, 2026
the-rabak/focused-ticket-priming
tools
VerifiedTrustedCommunity
Package one plan execution packet into a compact ticket-local execution packet with parent refs, scope fences, feature-home ownership, and evidence commands. Use when converting plans into local tickets or when execution needs one ticket-sized context pack without the full plan.
1SKILL.mdUpdated May 22, 2026
the-rabak/adversarial-plan-audit
testing
VerifiedTrustedCommunity
Run a deep adversarial review of plans and architecture before implementation. Use when validating strategy docs, contracts, roadmaps, and competitive positioning with scored findings and prioritized recommendations.
1SKILL.mdUpdated May 20, 2026
the-rabak/adversarial-plan-audit
testing
VerifiedTrustedCommunity
Run a deep adversarial review of plans and architecture before implementation. Use when validating strategy docs, contracts, roadmaps, and competitive positioning with scored findings and prioritized recommendations.
1SKILL.mdUpdated May 14, 2026