메뉴
Start a fix-oriented Ito change proposal with fix-biased intake and schema recommendations.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Implement Ito Lite markdown changes by reading proposal/spec/design/tasks artifacts and updating manual task statuses. Use when applying or executing a prompt-only Ito Lite change without the ito CLI.
Archive completed Ito Lite changes by manually merging spec deltas into current specs and moving the change to archive. Use after implementation and verification when no ito CLI is available.
Create prompt-driven Ito Lite change proposal packages in markdown. Use for drafting proposal.md, spec deltas, optional design.md, and tasks.md without the ito CLI or validation executable.
Review Ito Lite markdown proposal packages before implementation. Use to check proposal.md, spec deltas, design.md, and tasks.md for consistency, risk, testability, and manual validation without the ito CLI.
Initialize a markdown-only Ito Lite workspace with no executables. Use when setting up prompt-driven change proposals, creating .ito-lite/project.md, or preparing a repo for Ito-style specs, changes, and tasks without the ito CLI.
Coordinate the prompt-only Ito Lite workflow for proposals, specs, tasks, reviews, implementation, and archive without the ito executable. Use when the user asks for Ito-style planning, change proposals, lightweight specs, or markdown-only change management.
| 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.