Menú
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when the user asks to review a pull request or diff with a structured Codex CLI workflow using parallel review passes and filtered actionable findings.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
| name | dispatching-parallel-agents |
| description | Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. |
When you have multiple unrelated failures or investigations, handle them in parallel instead of forcing one agent to juggle everything.
Core principle: one agent per independent problem domain.
ext spawn_agent(role=explorer, task="Investigate agent-tool-abort.test.ts failures") spawn_agent(role=explorer, task="Investigate batch completion behavior failures") spawn_agent(role=explorer, task="Investigate tool approval race conditions")
