renzu

CLI 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

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Review and validate Ito changes, specs, or implementations. Use when the user wants a quality check, code review, or validation of project artifacts.

Use when executing implementation plans with independent tasks in the current session using subagents

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use Ito tasks CLI to manage tasks.md (status/next/start/complete/shelve/add).

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when discovering, finding, invoking, or loading skills. Ensures skills are invoked BEFORE responding. Establishes skill priority and usage patterns for OpenCode, Claude Code, and Codex.

Ito workflow delegation - delegates all workflow content to Ito CLI instruction artifacts.

Use when creating, designing, planning, proposing, or specifying a feature, change, requirement, enhancement, fix, modification, or spec. Use when writing tasks, proposals, specifications, or requirements for new work.

Use when creating new skills, editing existing skills, or verifying skills work before deployment