deep-interview

Requirements gathering uses Socratic questioning to iteratively ask targeted questions, exposing hidden assumptions and defining exact scope. It mathematically scores clarity across goals, constraints, and success criteria to ensure ideas are fully crystallized before planning.

The Socratic method for requirements gathering employs iterative questioning to expose hidden assumptions and define exact scope. It mathematically scores clarity across Goal, Constraints, Success Criteria, and Context dimensions to eliminate ambiguity.

To gather requirements for modifying an existing codebase, use a Socratic deep interview that adapts its questioning to existing code context. This brownfield approach ensures new specifications account for current system constraints before execution.

You measure ambiguity in software specifications by applying mathematical ambiguity scoring across Goal, Constraints, Success Criteria, and Context dimensions. The system blocks planning progression until a defined low ambiguity threshold is achieved.

Yes, you can use deep-interview for greenfield development planning as it explicitly supports new projects. It conducts rigorous interviews to define exact behaviors and success criteria before handing off to execution pipelines.

You should not use Socratic questioning for requirements gathering when your idea already meets clarity thresholds across goals, constraints, and context. It is designed specifically to resolve vagueness and will block progression if ambiguity is already low.