How It Works

The user begins with the vision and intended outcome. The agent then acts as an interviewer rather than an implementer. It asks questions, challenges vague statements, and introduces issues the user may not have considered.

A useful prompt pattern is to ask the agent to identify the most consequential decisions across product design, software design, and architecture, then interview the user about them. The process continues until the important ambiguities have been resolved and the agent can restate the intended system accurately.

This procedure can precede several downstream artifacts:

1. A shared description of the mission and constraints.
2. A product requirements document.
3. A set of individual issues or tasks.
4. An implementation sequence.

The interview is especially useful for planning, complicated implementations, and unscoped work.

These are situations where the human should remain in the loop because each answer can change the next question and alter the eventual design.