菜单
Use when executing implementation plans with independent tasks in the current session using subagents
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | subagent-driven-development |
| description | Use when executing implementation plans with independent tasks in the current session using subagents |
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
ito-apply-change-proposal)vs. ito-apply-change-proposal:
ito tasks complete <change-id> <task-id>ito-finishing-a-development-branch# Get the change context
ito agent instruction apply --change <change-id>
# Read tasks.md
ITO_ROOT="$(ito path ito-root)"
cat "$ITO_ROOT/changes/<change-id>/tasks.md"
# Extract all tasks with full text and context upfront
ito tasks start <change-id> <task-id>
Provide:
Pick an implementer agent tier based on task complexity:
ito-quick: small, localized changesito-general: most tasks (default)ito-thinking: complex refactors, tricky bugs, high-risk editsImplementer uses TDD:
Dispatch spec reviewer subagent with:
Reviewer checks:
If issues: implementer subagent fixes, re-review until ✅
Dispatch code quality reviewer subagent with:
Reviewer checks:
If issues: implementer subagent fixes, re-review until ✅
ito tasks complete <change-id> <task-id>
If more tasks: repeat from step 1
If done: dispatch final reviewer, then use ito-finishing-a-development-branch
./implementer-prompt.md - Dispatch implementer subagent./spec-reviewer-prompt.md - Dispatch spec compliance reviewer subagent./code-quality-reviewer-prompt.md - Dispatch code quality reviewer subagentNever:
If subagent asks questions:
If reviewer finds issues:
Required workflow skills:
ito-using-git-worktrees - Set up isolated workspace before startingito-write-change-proposal - Creates the plan this skill executesito-requesting-code-review - Code review template for reviewer subagentsito-finishing-a-development-branch - Complete development after all tasksSubagents should use:
ito-test-driven-development - Subagents follow TDD for each taskAlternative workflow:
ito-apply-change-proposal - Use for human-in-loop execution with batch checkpointsCLI for the Renzu MCP server. Call tools, list resources, and get prompts.
Use when implementing, executing, applying, building, coding, or developing a feature, change, requirement, enhancement, fix, or modification. Use when running tasks from a spec, proposal, or plan.
You MUST use this before any creative work - creating features, proposing changes,building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Create atomic git commits aligned to Ito changes. Use when you want to commit work after applying a change, optionally with auto-mode.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup