iter

Usage

Start a new session after installation and ask your coding tool to use iterate-product.

Reports follow the conversation language. New CLI cycles default to English; existing Chinese cycles retain their language when migrating storage.

Once you ask to develop the chosen scope, Iter completes implementation, necessary verification, and review, then closes the cycle automatically. Your next iteration request starts a fresh cycle by default; you do not need to say "start another iteration". Unfinished work resumes from its saved state. Asking about a previous result only reads that result.

Explore what to build next:

Use iterate-product to propose 2–3 concrete improvements for this product. Explain the user benefit, smallest scope, acceptance criteria, and risks. Recommend one for me to choose.

Deliver a feature you have already chosen:

Use iterate-product to add search history to this project, keeping at most 10 entries and supporting a clear action.
You may implement this scope and create isolated test data in a temporary directory. Verify deduplication, the entry limit, and clearing. Complete implementation, tests, and review.

Resume a saved iteration:

Use iterate-product to resume the saved product iteration. Continue within the approved scope and ask only when a material decision changes.

Iter stores state, reports, proposal inputs, and generated evidence outside your project, under ~/.iter by default. Each workspace has separate storage based on its resolved path. Set ITER_HOME to an absolute directory outside the workspace to override the base directory. The helper's read-only paths --workspace command shows the exact locations before initialization. Your existing source files and referenced evidence stay in place.

The host needs write access to that workspace's storage_root; Iter does not fall back to writing workflow files into the project. Existing .product-loop/ cycles need explicit migrate; moving a workspace uses relocate. See the storage and migration guide. Saved authorization is reused for unchanged scope. Publishing, external communication, and destructive operations require authorization for those actions.

Cancel or pause: say “Cancel this iteration” to end the current cycle while keeping its evidence. Say “Pause here; I will resume later” to keep the cycle active. Cancellation does not undo code changes. One active cycle per workspace; simultaneous writers are not supported.