菜单
Use Ito tasks CLI to manage tasks.md (status/next/start/complete/shelve/add).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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.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.
Archive a completed change and update main specifications. Use when the user has finished implementing and wants to integrate the change into the main codebase.
Run an ito ralph loop for a change, module, or repo-ready sequence, with safe defaults and automatic restart context on early exits.
Use when creating and writing an Ito change proposal (new change or existing change id). Delegates to Ito CLI instruction artifacts.
Conduct structured research for feature development, technology evaluation, or problem investigation. Use when the user needs to explore options, analyze trade-offs, or investigate technical approaches.
Review and validate Ito changes, specs, or implementations. Use when the user wants a quality check, code review, or validation of project artifacts.