메뉴
Use Ito tasks CLI to manage tasks.md (status/next/start/complete/shelve/add).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Manage remote Kocao agent sessions from an AI assistant. Use when: listing running agents, starting a new remote agent, checking agent status, viewing agent logs, stopping an agent session, or sending a prompt to a running remote agent.
Fast trigram-indexed code search across the entire repository using Zoekt (the engine behind GitHub and Sourcegraph code search). Use INSTEAD OF grep/ripgrep for broad codebase searches. Supports regex, literal strings, file filters, and symbol queries. Auto-installs zoekt binaries and auto-indexes the repo on first use.
Apply a Change Proposal. Triggered by the user saying "Apply change <change-id>" or "Implement change <change-id>". Use when implementing, executing, applying, building, coding, or developing a feature, change, requirement, enhancement, fix, or modification. Use when running tasks from a spec, proposal, or plan.
You MUST use this before any creative work - creating features, proposing changes,building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — presents structured options for merge, PR, or cleanup
Run an ito ralph loop for a specific change (or module/repo sequence), with safe defaults and automatic restart context on early exits.
| 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.