ワンクリックで
ito-loop
Run an ito ralph loop for a change, module, or repo-ready sequence, with safe defaults and automatic restart context on early exits.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Run an ito ralph loop for a change, module, or repo-ready sequence, with safe defaults and automatic restart context on early exits.
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-loop |
| description | Run an ito ralph loop for a change, module, or repo-ready sequence, with safe defaults and automatic restart context on early exits. |
Keep Ralph available by default for one change, one module, or the next ready work item. Parse identifiers with ito util parse-id; quote parsed input and never use eval.
Before change-mode iteration, resolve the guarded worktree with ito worktree ensure --change "<change-id>", enter it, and run ito change preflight "<change-id>" --for execute. For module and ready-work modes, let Ralph apply the same gate after each dynamic selection. Treat readiness failures as terminal for the attempt.
Build one command with bounded defaults: five iterations, a 15-minute timeout, and at most two outer restarts for restartable early exits.
ito ralph --no-interactive --harness <harness> --change <change-id> --max-iterations 5 --timeout 15m
ito ralph --no-interactive --harness <harness> --module <module-id> --max-iterations 5 --timeout 15m
ito ralph --no-interactive --harness <harness> --continue-ready --max-iterations 5 --timeout 15m
Do not wrap Ralph in an unbounded loop. Add restart context only when ito ralph --status and ito tasks status provide meaningful recovery evidence. Report final status after success or bounded exhaustion.
For multi-change orchestration, render and follow:
ito agent instruction orchestrate
Treat .ito/user-prompts/orchestrate.md as additive project policy. Preserve dependency and gate order, run state, coordinator-only responsibilities, remediation, and resume semantics. Missing project guidance triggers inline setup from the same authoritative instruction; no setup or workflow skill is generated.