メニュー
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.
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-archive |
| description | 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 the CLI-generated archive instructions for a specific change.
Rules
Steps
Determine the target change ID:
ito list --completed --json
ito list --partial
ito list --pending
ito list to see all changes and their status."Generate instructions (source of truth):
ito agent instruction archive --change "<change-id>"
Follow the printed instructions exactly.
After archive/spec sync succeeds, refresh relevant .ito/wiki/ topic pages when .ito/wiki/index.md exists. Prefer topic-page synthesis that links to the archived change, specs, modules, research, architecture notes, and documentation instead of creating one wiki page per archived change. If wiki coverage is absent, stale, or contradictory, note the risk and continue from raw Ito artifacts; wiki refresh is recommended follow-through, not an archive blocker.