Menú
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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
Karpathy-inspired guidelines: Think before coding, Simplicity first, Surgical changes, Goal-driven execution
Write an actionable markdown plan before implementation. Bite-sized tasks, exact paths, complete code.
Write clear Conventional Commits. Imperative subject, explain why not what, one logical change per commit.
Optimize based on measurement, never guesswork. Profile first, fix the real bottleneck, verify the win.
Refactor code without changing behavior. Small steps, green tests after every change, no mixing with feature work.
Review PRs on GitHub: read diffs, leave inline comments, approve or request changes.
| name | executing-plans |
| description | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
| conditional | true |
When the user has an existing plan file or asks you to execute a plan:
.cove/plans/ file or the plan the user referencestodowrite to create tasks matching the plan structure
depends:<task-id> for dependencies between tasksexecute_plan with parallel:true for independent tasksdepends: prefix in the same level) in parallel