Menu
Use when you need stable absolute paths (project/worktree/.ito/worktrees) without embedding machine-specific paths into committed files
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-path |
| description | Use when you need stable absolute paths (project/worktree/.ito/worktrees) without embedding machine-specific paths into committed files |
Use ito path ... to resolve filesystem paths at runtime.
This is the preferred way to:
# Stable root shared across worktrees
ito path project-root
# Current working worktree root (fails in bare repos)
ito path worktree-root
# Absolute path to the `.ito` directory
ito path ito-root
# Worktrees root (fails if worktrees disabled)
ito path worktrees-root
# A specific worktree directory
ito path worktree --main
ito path worktree --branch <name>
ito path worktree --change <change-id>
# Bundle of roots
ito path roots
ito path roots --json
project-root is stable across linked worktrees.worktree-root is the current working tree root.ito-root is the .ito directory for the current invocation.In a bare/control repo directory (no working tree), Ito should be run from a worktree. ito path worktree-root exits non-zero and prints a helpful error.
ito path project-root --json
Returns:
{ "path": "/abs/path" }
Committed files (templates/skills) should use repo-relative paths.
If an absolute path is needed at runtime (for agent output or scripts), instruct the caller to use ito path ....