deep-interview

To convert vague ideas into testable specifications, you use a structured Socratic interview that asks one question at a time to surface hidden assumptions. This process scores ambiguity across dimensions until it falls below 20%, producing a formal markdown spec for downstream planning.

The Socratic method for requirements gathering is a structured interview process that identifies the weakest clarity dimension and drives targeted questioning. It tracks ontology to stabilize core concepts and persists state to safely resume interviews after interruptions.

Yes, you can anchor requirements gathering to an existing codebase. The interview operates in both greenfield and brownfield contexts, using your available codebase to ground the Socratic questioning and produce more accurate testable specifications.

You measure ambiguity during specification planning through transparent ambiguity scoring across multiple dimensions. The interview process tracks gaps and progress, continuing targeted questioning until overall ambiguity drops below 20%.

Yes, the deep interview process integrates with execution and planning tools via omc-plan and autopilot pathways. It outputs a formal specification markdown file that serves as direct input for downstream planning, with optional challenge modes available.

A limitation of using a Socratic interview for requirements gathering is that it requires sustained interaction to reduce ambiguity below 20%. While state persistence allows resuming after interruptions, the process needs sufficient rounds to detect concept convergence and stabilize the ontology.