菜单
Unified entry point for ito commands with intelligent skill-first routing and CLI fallback.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | ito |
| description | Unified entry point for ito commands with intelligent skill-first routing and CLI fallback. |
Ito has six lifecycle destinations beneath this root entrypoint:
| Intent | Retained skill |
|---|---|
| clarify, plan, or propose | ito-proposal |
| investigate or synthesize | ito-research |
| implement an accepted proposal | ito-apply |
| review or verify | ito-review |
| archive and promote accepted specs | ito-archive |
| iterate, Ralph, or orchestrate | ito-loop |
Parse the first intent and preserve every remaining argument unchanged. Route only to this fixed table. If the matching retained skill is missing, report an installation error and recommend ito init --upgrade; do not silently execute a different phase.
Helper-shaped requests are phase intents, not separate skills: feature/fix/intake/planning go to ito-proposal; worktrees/tasks/commits go to ito-apply; testing/verification go to ito-review; finish goes to ito-archive; orchestration goes to ito-loop.
Use direct CLI fallback for operational commands such as ito list, ito path, ito config, ito status, ito validate, ito update, and ito plan init|status. Repository cleanup guidance comes from ito agent instruction cleanup; managed refresh uses ito init --upgrade. Preserve CLI argument order and errors.
An explicit retired skill request receives a short replacement explanation using the lifecycle table. Tmux integration was removed and has no Ito replacement. There is no wildcard skill discovery, filesystem cache, or dynamically constructed ito-* activation.
For first-run project orientation, render ito agent instruction project-setup. User-authored skills remain outside the Ito-managed inventory.
