القائمة
Ito workflow delegation - delegates all workflow content to Ito CLI instruction artifacts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | ito-workflow |
| description | Ito workflow delegation - delegates all workflow content to Ito CLI instruction artifacts. |
This skill delegates workflow operations to the Ito CLI.
Principle: The Ito CLI is the source of truth for workflow instructions. Skills should be thin wrappers that invoke the CLI and follow its output.
ito create change "<name>" --module <module-id>
ito list [--json]
ito list --ready # Show only changes ready for implementation
ito list --pending # Show changes with 0/N tasks complete
ito list --partial # Show changes with 1..N-1/N tasks complete
ito list --completed # Show changes with N/N tasks complete
ito status --change "<change-id>"
ito agent instruction proposal --change "<change-id>"
ito agent instruction specs --change "<change-id>"
ito agent instruction tasks --change "<change-id>"
ito agent instruction apply --change "<change-id>"
ito agent instruction review --change "<change-id>"
ito agent instruction archive --change "<change-id>"
# Worktrees / multi-branch workflow (per-developer)
ito agent instruction worktrees
ito tasks status <change-id>
ito tasks next <change-id>
ito tasks ready # Show ready tasks across all changes
ito tasks ready <change-id> # Show ready tasks for a specific change
ito tasks start <change-id> <task-id>
ito tasks complete <change-id> <task-id>
ito agent instruction commandito tasks to track progressito-write-change-proposal - Create new changesito-apply-change-proposal - Implement changesito-review - Review changesito-archive - Archive completed changesito-tasks - Manage tasksito-commit - Create commitsCLI 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