Menú
Direct implementation mode for small, known fixes or UI updates. Bypasses heavy diagnosis or PRD creation.
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
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a spec or set of tickets.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
| name | tweak |
| description | Direct implementation mode for small, known fixes or UI updates. Bypasses heavy diagnosis or PRD creation. |
Use for small known fixes.
/zoo-verify before /zoo-code-review before /zoo-commit-and-document. Do not auto-launch. Otherwise offer /zoo-commit-and-document only after user satisfied.Call attempt_completion with:
Do NOT use ask_followup_question or write results as plain text without calling the tool.
Before broad reads, locate relevant files/symbols with list_files, search_files, or codebase_search.
Prefer targeted read_file ranges or indentation/block reads once the relevant area is known.
Read full files only when structure, ordering, or surrounding context is required for correctness.
Do not re-read unchanged files; use prior findings unless the file changed.
For small changes, audit only the named files and nearby call sites. Expand search only if the first audit shows hidden dependencies.