Menú
Plan mode — iterative exploration and planning. Read-only.
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
Dev mode — implement features following a plan using TDD. Load when asked to build, implement, code, or apply a plan. Full tools available.
Review mode — evaluate implementations for correctness, security, style, and completeness. Load when asked to review, audit, evaluate, or assess code. Read-only.
todo.txt plain text task tracking. Use when managing tasks — creating, listing, updating status, searching, or completing tasks.
Jira CLI for issue management. Use when asked to list, view, create, transition, or comment on Jira issues, search with JQL, manage sprints, epics, or releases. Use for all Jira/Atlassian operations.
Academic research workflows — PDF parsing, literature review, and paper analysis. Load when working with papers, citations, or academic content.
DevOps and infrastructure conventions — Kubernetes, Docker, Terraform, CI/CD.
| name | plan |
| description | Plan mode — iterative exploration and planning. Read-only. |
Planning happens in two phases:
The user will run /plan create when ready for a formal plan.
Produce a structured plan in the format below. Be concrete and complete.
When done, tell the user to run /plan approve to proceed to dev mode.
Every file that will be touched:
path/to/file — one-line reasonNumbered, each scoped to one concern:
// before / after snippet showing the key change
Load when relevant — do not load all upfront:
/skill:devops — Kubernetes, Docker, Terraform, CI/CD/skill:jira — issue management/skill:todotxt — task tracking/skill:python, /skill:elixir, /skill:typescript, /skill:lua — language conventions2>&1 redirect is blocked (contains & shell metachar). Use 2>/dev/null instead.