菜单
Use for sequential per-task subagent delegation within one Ito change in the current session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ito-subagent-driven-development |
| description | Use for sequential per-task subagent delegation within one Ito change in the current session. |
Use this only when implementing one Ito change in the current session with delegated worker agents.
ito agent instruction apply --change <change-id> and follow the rendered apply instruction for task tracking, worktree rules, and testing policy.ito tasks ready/start/complete for task state; do not edit tasks.md directly.ito agent instruction finish --change <change-id> or the ito-finish skill.Do not duplicate the full apply workflow here; ito agent instruction apply --change <change-id> is the source of truth.
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.