القائمة
Resolve all pending CLI todos using parallel processing, compound on lessons learned, then clean up completed todos.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Optimize Claude Code permissions by finding safe Bash commands from session history and auto-applying them to settings.json. Can run from any coding agent but targets Claude Code specifically. Use when experiencing permission fatigue, too many permission prompts, wanting to optimize permissions, or needing to set up allowlists. Triggers on "optimize permissions", "reduce permission prompts", "allowlist commands", "too many permission prompts", "permission fatigue", "permission setup", or complaints about clicking approve too often.
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
[BETA] Transform feature descriptions or requirements into structured implementation plans grounded in repo patterns and research. Use when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', or when a brainstorm/requirements document is ready for technical planning. Best when requirements are at least roughly defined; for exploratory or ambiguous requests, prefer ce:brainstorm first.
Transform feature descriptions into well-structured project plans following conventions
Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees
Create or edit Claude Code skills with expert guidance on structure and best practices
| 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.
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.
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.
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:
Always run all in parallel subagents/Tasks for each Todo item.
GATE: STOP. Verify that todos have been resolved and changes committed. Do NOT proceed to step 5 if no todos were resolved.
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.
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]