メニュー
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.
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-research |
| description | 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. |
Use the phase resources in this directory for stack, feature, architecture, pitfalls, security, scale, edge-case, and synthesis work. Save source investigations under .ito/research/<topic>/ or change reviews under .ito/changes/<change-id>/reviews/.
Read .ito/wiki/index.md when present. Treat .ito/wiki/ as synthesized navigation: cite the underlying spec, change, research, code, or documentation and call out stale or contradictory coverage. Fall back to raw Ito artifacts rather than blocking.
Use Ito's configured, provider-neutral memory operations when helpful:
ito agent instruction memory-search --query "<terms>" --limit 10
ito agent instruction memory-query --query "<question>"
Memory is guidance, not the source of truth. Current specs, code, and rendered instructions win conflicts. Durable capture belongs to the archive phase.
Finish with a concise recommendation containing evidence, alternatives, trade-offs, risks, and confidence. Link the synthesis from the proposal/design when research informs a change, and update wiki topic/query artifacts only when the result has durable reuse value.