deep-interview

To clarify vague product ideas into actionable requirements, use a Socratic questioning loop that surfaces hidden assumptions and targets the weakest clarity dimension each round until ambiguity drops below a gating threshold, producing a crystallized spec.

The Socratic method for requirements gathering involves an agent asking one focused question at a time to explore goals, constraints, success criteria, and context, mathematically measuring ambiguity reduction before finalizing a specification.

For brownfield project requirements gathering, the process supports lightweight codebase context collection to understand existing structures, guiding discovery alongside greenfield projects before bridging to planning and automation.

Yes, you can adjust the mathematical ambiguity gating threshold during a requirements interview, controlling how strictly the session reduces uncertainty before outputting a crystallized spec and offering execution options.

The best way to bridge requirements gathering to project planning uses a three-stage pipeline: deep-interview crystallizes the spec, omc-plan handles planning, and autopilot executes, with state persistence and ontology tracking maintained throughout.

You should avoid automated Socratic questioning if your idea already has a clear, actionable specification, as the process targets the weakest clarity dimensions and enforces a gating threshold specifically to resolve initial ambiguity.