菜单
Start a fix-oriented Ito change proposal with fix-biased intake and schema recommendations.
用 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-fix |
| description | Start a fix-oriented Ito change proposal with fix-biased intake and schema recommendations. |
Use this when the user frames the work as a fix, regression, correction, or supporting platform/tooling/infrastructure change that should be handled like a fix.
If the user already provided a change ID, skip to Step 5 (Continue with ito-proposal) — the change already exists.
Drive proposal creation through a fix-oriented intake lane without locking the user into a specific schema.
ito-proposal-intake.minimalist for bounded fixes and small supporting platform or infrastructure changestdd for regression-oriented changes where test-first work is safestspec-driven if the fix turns out to be broad, architectural, or still ambiguousevent-driven if the change is centered on event or message workflow behaviorito-proposal using the intake summary as the shared understanding.ito-feature or ito-brainstorming.ito-fix is an opinionated front door, not a separate schema.ito-proposal lane.