ワンクリックで
ito-list
List Ito changes, archived changes, specs, or modules with status summaries and intelligent interpretation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
List Ito changes, archived changes, specs, or modules with status summaries and intelligent interpretation.
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-list |
| description | List Ito changes, archived changes, specs, or modules with status summaries and intelligent interpretation. |
Use ito list and ito list-archive to display project items and interpret the results for the user.
Goal: run the right listing command, summarize the output clearly, and suggest the next sensible action.
CLI Reference
ito list [OPTIONS]
ito list-archive [--json]
Item types (default: changes):
--changes List changes (default)
--specs List specs
--modules List modules
Progress filters (changes only, mutually exclusive):
--ready Changes ready for implementation (have proposal, specs, tasks, and pending work)
--completed Changes with all tasks done
--partial Changes with some but not all tasks done
--pending Changes with no tasks started
Other options:
--sort <ORDER> Sort order: recent (default) or name
--json Output as JSON
Parse user intent from the arguments:
ito list-archive when they ask for archived changes--json for structured output that is easier to interpret programmaticallyRun the CLI command:
ito list or ito list-archive invocationito list --ready --json, ito list --specs, or ito list-archivePresent and interpret results:
Suggest next actions based on the results:
/ito-apply <change-id> to start implementing/ito-apply <change-id>/ito-archive <change-id>ito create change# List all changes (default)
ito list
# List only changes ready for implementation
ito list --ready
# List specs
ito list --specs
# List changes with JSON output for analysis
ito list --json
# List completed changes (candidates for archiving)
ito list --completed
# List modules
ito list --modules
# List archived changes
ito list-archive
--json when you need to programmatically interpret results.--ready, --completed, --partial, --pending) only apply to changes, not specs or modules.ito init.