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 continue without migration.

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.

State is saved in .product-loop/state.json; reports live alongside it in the cycle directory. Existing authorization is reused. 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.