The product phase

The product phase is about defining what the change is. Not how it's built. Not what files change. Just what the user experience should be.

When you start an iteration, Itera's product agent reads your codebase to understand the current product. It then compares that against your prompt to figure out where the gaps are. Wherever your intent has multiple possible interpretations, the agent asks a question.

Product questions

Questions appear inline in the iteration. Each one has:

• A short label, for example Question / Product / responsive-scope
• The question itself
• A list of suggested answers
• A Custom reply option for when none of the suggestions fit
• A Submit answer button

You can navigate between questions with the arrows in the top right of the question card. There's no requirement to answer every question. You only need enough clarity for the system to feel confident about your intent.

The summary and specifications

As you answer questions, two sections of the iteration update in real time:

• Summary. A short description of what's being built, in your own words.
• Specifications. A structured list of changes, grouped by type (User Experience, User UI, and so on).

You can also send free text into the chat at any point to add context, change scope, or clarify something the agent didn't ask about.

Generating a prototype

You'll see a Generate Prototype button in the iteration. Clicking it spins up a live, interactive version of your product with the proposed changes applied. See Prototyping for the full flow.

Moving to engineering

When the iteration feels well-defined and you're ready to hand off, click the action button to move to the Engineering phase. Itera will suggest reassigning to an engineer, but you can keep the iteration yourself if you prefer.