菜单
Use when creating and writing an Ito change proposal (new change or existing change id). Delegates to Ito CLI instruction artifacts.
用 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.
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.
Unified entry point for ito commands with intelligent skill-first routing and CLI fallback.
| name | ito-proposal |
| description | Use when creating and writing an Ito change proposal (new change or existing change id). Delegates to Ito CLI instruction artifacts. |
Own intake, feature/fix framing, brainstorming, pre-proposal planning, and proposal/spec/design/task scaffolding.
Inspect relevant brownfield specs, code, history, and .ito/wiki/index.md. Ask one focused question at a time and use the least-sufficient discovery depth.
Confirm the problem, success criteria, scope, exclusions, risks, simpler alternatives, and YAGNI trade-offs. Use ito-research when evidence or technology choices remain unresolved, then carry a concise research handoff into the proposal or design.
Make module confirmation mandatory. Run ito list --modules, then wait for the user to choose an existing module, a new module, or a new sub-module. Never silently use module 000.
Keep durable exploration under .ito/planning/. ito plan init and ito plan status are direct workspace commands, not separate skills.
Render ito agent instruction schemas, recommend the best-fit schema, and create the change only after module confirmation:
ito create change "<change-name>" --module <module-id> --schema <schema>
For an existing change, skip creation. Render every authoritative artifact instruction and follow it exactly:
ito agent instruction proposal --change "<change-id>"
ito agent instruction specs --change "<change-id>"
ito agent instruction design --change "<change-id>"
ito agent instruction tasks --change "<change-id>"
Run ito validate <change-id> --strict and review the proposal-only package. Integrate it using changes.proposal.integration_mode:
pull_request (default): push, review, and merge a proposal-only PR.direct_merge: after explicit approval, merge the proposal-only commit through the repository's guarded Git workflow.Do not implement, start tasks, or launch workers from the proposal branch. Verify the handoff with ito change preflight "<change-id>" --for prepare --refresh, then hand the integrated proposal to ito-apply.