deep-interview

To turn a vague project idea into a precise specification, you can use a Socratic questioning loop that targets your weakest clarity dimensions, settling assumptions one question at a time until a mathematical ambiguity threshold is met.

Socratic ambiguity gating is a requirements-gathering process that mathematically scores goal, constraint, and success criteria clarity, blocking pipeline handoff until ambiguity drops below a defined threshold like 20%.

You score ambiguity by combining goal, constraint, and success criteria clarity into a calculated threshold, using ontology tracking to show convergence and gate execution until specifications reach sufficient precision.

Yes, after the interview state is persisted and specifications are crystallized, the output can be handed off directly to downstream planning and autopilot pipelines or autoresearch when prompted.

Yes, the mathematical ambiguity scoring applies to brownfield engineering requests by adding context clarity to the goal, constraint, and success criteria dimensions to ensure thorough requirements before automation proceeds.

You should avoid Socratic questioning for requirement specifications if your project idea is already well-defined, as the ambiguity gating threshold is designed to reduce vague assumptions rather than process precise inputs.