Menú
Track tasks during multi-step work. Each task is a separate scratchpad entry so updates are atomic and nothing gets dropped.
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
System design and architecture decisions. Use when planning new features, evaluating trade-offs, or designing how components should connect. Proposes 2-3 approaches and recommends one.
Smart commit workflow. Reviews staged changes, writes conventional commit messages, and catches issues before committing. Use when ready to commit work.
Quality review of completed work. Use after making changes and before claiming completion. Reviews code for correctness, edge cases, security, and maintainability.
Systematic debugging workflow. Use when diagnosing bugs, test failures, or unexpected behavior. Follows a rigorous reproduce → isolate → hypothesize → fix → verify cycle.
Systematic multi-agent research. Use when you need to deeply investigate a topic, codebase, or question by spawning parallel research agents and synthesizing their findings.
Deep code explanation. Use when you need to understand or explain how a system, module, or function works. Traces data flow, maps dependencies, and explains design decisions.
| name | todo |
| description | Track tasks during multi-step work. Each task is a separate scratchpad entry so updates are atomic and nothing gets dropped. |
You are managing a todo list. Each task is stored as a separate scratchpad entry so individual updates never clobber other items.
Each task is a scratchpad key todo#N with a value like:
[ ] Fix auth middleware
[x] Add rate limiting
Add a task: Write the next available number — scratchpad_write("todo#1", "[ ] Fix auth middleware").
Complete a task: Overwrite it — scratchpad_write("todo#3", "[x] Add rate limiting").
Remove a task: Delete it — scratchpad_delete("todo#3"). Gaps in numbering are fine.
todo#* keys.todo#N entries for sub-tasks.