deep-interview

To reduce ambiguity in requirements, a Socratic questioning process exposes hidden assumptions one question at a time. This structured requirement-gathering approach dynamically reveals assumptions to crystallize vague ideas into formal specifications before execution.

A Socratic interview for requirements gathering is a structured, one-question-at-a-time dialogue that enforces explicit ambiguity gates. It maintains an interview transcript to expose hidden assumptions, producing a formal spec and ontology for rigorous validation.

To start requirement gathering for a vague greenfield idea, initiate a deep interview process. It supports greenfield scenarios by conducting targeted Socratic questioning to transition your undefined concept into a crystallized formal specification ready for planning.

Yes, you can use Socratic interviewing for brownfield projects. The process supports brownfield scenarios by applying ontology-based stability checks to ensure requirement changes extracted during the interview result in safe, validated modifications.

The best way to transition from requirements gathering to automated execution is using a 3-stage pipeline: deep-interview for requirement crystallization, omc-plan for planning, and autopilot for execution. This pipeline ensures specs are validated before automation begins.

You should not use a Socratic interview approach for specification generation when your requirements are already fully explicit and validated. The process enforces ambiguity gates designed specifically to process vague ideas, making it redundant for already crystallized specs.