deep-interview

To turn vague product ideas into precise engineering specifications, this Skill applies a Socratic interview loop with ambiguity scoring that iteratively targets the weakest clarity dimensions until a structured spec is crystallized. It prevents wasted build cycles by uncovering hidden assumptions before execution begins.

The best way to gather requirements for an existing codebase is to use brownfield-aware onboarding that explores the codebase and maps relevant areas before interviewing. This ensures Socratic questioning matches the existing system architecture and surfaces hidden assumptions specific to the current environment.

Ambiguity scoring in product discovery interviews works by iteratively evaluating clarity across goal, constraints, success criteria, and context dimensions. The Socratic loop targets the weakest dimension with structured questioning until ambiguity falls below a threshold, triggering spec crystallization and gated execution-bridge selection.

To transition a finalized specification into an execution plan, use execution bridge selection to route the crystallized spec into downstream workflows like ralplan or omg-autopilot. This gated handoff only triggers once ambiguity scoring falls below the required threshold, ensuring execution readiness.

You should not use automated Socratic questioning for requirement gathering when your success does not depend on uncovering hidden assumptions before execution, or when dealing with scenarios outside product, engineering, and workflow definition that lack the need for mathematically clear specifications.