Skip to content
Automation
Skill

/prod-review-todoist

Review and organize Todoist tasks in the Evolution project. Finds uncategorized, untranslated, or messy tasks and organizes them with proper categories, PT-BR translation, and actionable titles. Use when user says 'review todoist', 'organize tasks', 'todoist triage', 'clean up

From plugin
evo-nexus
520193 skills38 agents40 commands9 MCP
Install
$ npx -y skills add evolution-foundation/evo-nexus --skill prod-review-todoist --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/prod-review-todoist

Context preview

The summary Claude sees to decide when to auto-load this skill.

Review and organize Todoist tasks in the Evolution project. Finds uncategorized, untranslated, or messy tasks and organizes them with proper categories, PT-BR translation, and actionable titles. Use when user says 'review todoist', 'organize tasks', 'todoist triage', 'clean up

SKILL.md

prod-review-todoist.SKILL.md
name: prod-review-todoist
description: "Review and organize Todoist tasks in the Evolution project. Finds uncategorized, untranslated, or messy tasks and organizes them with proper categories, PT-BR translation, and actionable titles. Use when user says 'review todoist', 'organize tasks', 'todoist triage', 'clean up todoist', or similar."

Review Todoist — Evolution Project Triage

Skill to review and organize tasks in the Evolution Todoist project. Identifies uncategorized, English-only, generic, or disorganized tasks and fixes them directly.

Prerequisites

  • CLI `todoist` installed and authenticated
  • `Evolution` project existing in Todoist

Workflow

Step 1 — List Evolution project tasks

todoist tasks -p "Evolution"

Step 2 — Identify tasks that need organization

A task needs triage if it meets **any** of these criteria:

1. **No category** — does not have `[Categoria]` prefix in the title 2. **In English** — title is not in PT-BR 3. **Generic/vague** — title does not make clear what to do (ex: "update thing", "send docs") 4. **No context** — no comment with origin/objective (especially tasks from sync-meetings)

Step 3 — Organize each task

For each task that needs triage, apply:

3a. Categorize

Add `[Categoria]` prefix to the title. Available categories:

| Category | When to use | |---|---| | `[Produto & Tech]` | Development, bugs, features, infra, deploy, code | | `[Marketing]` | Content, campaigns, videos, social media, launches | | `[Sales]` | Pipeline, proposals, partnerships, leads, pricing | | `[Financial]` | Accounts, invoices, payments, financial metrics | | `[Operations]` | Internal processes, groups, access, team communication | | `[Strategy]` | OKRs, roadmap, analyses, strategic decisions | | `[Community]` | Discord, support, user feedback, beta testers | | `[Roadmap]` | Future roadmap items, feature evaluation |

3b. Translate to PT-BR

If the title is in English, translate to Brazilian Portuguese keeping clarity and objectivity.

**Before:** `Send event registration link to team member` **After:** `[Operação] Enviar link de inscrição do evento para membro do time`

3c. Make actionable

The title should make clear:

  • **What** to do (infinitive verb)
  • **For whom/where** (if applicable)
  • **Expected result** (if not obvious)

**Before:** `Upload web panel; grant team member access` **After:** `[Operação] Publicar painel web do evento e liberar acesso para membro do time`

3d. Apply the update

todoist update <task-id> --content "[Categoria] Título traduzido e acionável"

Step 4 — Execute directly

**Fundamental rule: execute the organization directly, without an intermediate report.**

Do not list tasks before organizing. Do not ask for confirmation on each one. Organize all at once and confirm at the end.

Step 5 — Save artifact

Save a short report to `workspace/daily-logs/[C] YYYY-MM-DD-todoist-review.md` com:

# Todoist Triage — YYYY-MM-DD

**Project:** Evolution
**Tasks reviewed:** {N}
**Organized:** {M} (categorized, translated, or rewritten)
**Already OK:** {K} (no changes needed)

## Organized Tasks

| Task | Before | After |
|--------|-------|--------|
| ... | ... | ... |

Create the directory `workspace/daily-logs/` if it does not exist.

Step 6 — Final report (short)

When finished, present only:

## Todoist Triage — Completed

**Project:** Evolution
**Tasks reviewed:** {N}
**Organized:** {M} (categorized, translated, or rewritten)
**Already OK:** {K} (no changes needed)

If the user wants to see details of what changed, they ask.

Important Rules

  • **Default project is always `Evolution`** — do not move tasks to other projects
  • **Always translate to PT-BR** — no exceptions
  • **Do not modify already organized tasks** (that already have `[Category]` and are in PT-BR)
  • **Do not complete or delete tasks** — only reorganize
  • **Do not create new tasks** — only edit existing ones
  • **Keep existing comments** — do not modify comments, only the title
  • **If unsure about the category**, use `[Operations]` as fallback
  • **Execute first, report after** — no intermediate report
Read more
Ships withevo-nexus

The open source operating system for AI-powered businesses

Get the whole plugin

Other skills on evo-nexus.