| name | ito-apply |
| description | Apply a Change Proposal.
Triggered by the user saying "Apply change <change-id>" or "Implement change <change-id>".
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.
|
Apply lifecycle
Apply only a reviewed proposal that satisfies the repository's main-first policy. Never substitute proposal files from a local feature branch, coordination state, or backend state.
-
Determine the full change ID. If missing, run ito list --ready; ask when more than one change is ready.
-
Confirm that the reviewed proposal is authoritative:
ito change preflight "<change-id>" --for prepare --refresh
Stop on failure and follow the reported remediation.
-
Keep the main/control checkout read-only. Create or reuse one dedicated full-ID worktree from main, protect locked worktrees, and never reuse one worktree for two changes. Then verify execution readiness:
CHANGE_DIR=$(ito worktree ensure --change "<change-id>") && \
cd "$CHANGE_DIR" && \
ito change preflight "<change-id>" --for execute
-
Render the source of truth and follow it exactly:
ito agent instruction apply --change "<change-id>"
-
Drive progress with ito tasks next|ready|start|complete; do not edit task state directly. Use scoped worker packets and self-review when delegating. Ralph remains available through ito-loop after execution readiness passes.
-
Follow RED/GREEN/REFACTOR and preserve task and acceptance scope. Make small, change-aligned commits and run relevant checks before every completion claim.
Hand completed implementation evidence to ito-review. Do not archive or integrate merely because task boxes are checked.
