Menú
Use Ito tasks CLI to manage tasks.md (status/next/start/complete/shelve/add).
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
Implement Ito Lite markdown changes by reading proposal/spec/design/tasks artifacts and updating manual task statuses. Use when applying or executing a prompt-only Ito Lite change without the ito CLI.
Archive completed Ito Lite changes by manually merging spec deltas into current specs and moving the change to archive. Use after implementation and verification when no ito CLI is available.
Create prompt-driven Ito Lite change proposal packages in markdown. Use for drafting proposal.md, spec deltas, optional design.md, and tasks.md without the ito CLI or validation executable.
Review Ito Lite markdown proposal packages before implementation. Use to check proposal.md, spec deltas, design.md, and tasks.md for consistency, risk, testability, and manual validation without the ito CLI.
Initialize a markdown-only Ito Lite workspace with no executables. Use when setting up prompt-driven change proposals, creating .ito-lite/project.md, or preparing a repo for Ito-style specs, changes, and tasks without the ito CLI.
Coordinate the prompt-only Ito Lite workflow for proposals, specs, tasks, reviews, implementation, and archive without the ito executable. Use when the user asks for Ito-style planning, change proposals, lightweight specs, or markdown-only change management.
| name | ito-tasks |
| description | Use Ito tasks CLI to manage tasks.md (status/next/start/complete/shelve/add). |
Use the ito tasks CLI to track and update implementation tasks for a change.
Rules
ito tasks ... over manual editing of tasks.md.start, shelve, unshelve, and add.[~] / ito tasks start, but no shelving); start/complete tasks by 1-based index.Common Commands
ito tasks status <change-id>
ito tasks next <change-id>
ito tasks ready # Show ready tasks across ALL changes
ito tasks ready <change-id> # Show ready tasks for a specific change
ito tasks ready --json # JSON output for automation
ito tasks start <change-id> <task-id>
ito tasks complete <change-id> <task-id>
ito tasks complete <change-id> <index>
ito tasks shelve <change-id> <task-id>
ito tasks unshelve <change-id> <task-id>
ito tasks add <change-id> "<task name>" --wave <n>
ito tasks show <change-id>
If tasks.md is missing
ito tasks init <change-id>tasks.md is normal. Prefer ito tasks ... directly, and use ito tasks sync pull <change-id> only when you explicitly need a local cache copy for inspection.If the user asks "what should I do next?"
ito tasks next <change-id>ito tasks ready to see all actionable tasksGuardrails
ito tasks status <change-id> and either resolve blockers or shelve the task (enhanced only).ito tasks shelve fails because the file is checkbox-only, explain that checkbox compat mode does not support shelving.ito tasks start fails in compat mode, it is usually because the task id is not a 1-based index, or another task is already in-progress.