Overview
Many implementation failures begin before any code is written. The idea is underspecified, consequential decisions remain hidden, and the agent fills the gaps with assumptions. An adversarial interview procedure addresses this by making the agent question the user until both sides share a sufficiently concrete understanding of the work.
The goal is not to generate a long plan immediately. The goal is to expose uncertainty, contradictions, missing constraints, and decisions that will shape the product or architecture.