deep-interview

To clarify vague product requirements into executable specifications, a guided Socratic interview probes intent, scope, constraints, and acceptance criteria. This method extracts explicit, testable boundaries from ambiguous initial requests.

Defining non-goals and decision boundaries is best achieved through structured clarification interviews that stress-test assumptions. This ensures explicit scope limits are documented before downstream planning and execution stages begin.

Yes, you can use a Socratic interview to preserve brownfield context. It reuses context snapshots and generates formal specs with contextual references, ensuring traceability for downstream handoffs in existing codebases.

Generate traceable artifacts by running a structured clarification process that outputs a transcript under .omx/interviews and a formal spec under .omx/specs. These artifacts store explicit scope and acceptance criteria for handoff.

Yes, the specification interview process supports escalation modes to stress-test assumptions. It also features readiness gates and multiple depth profiles to ensure vague ideas are fully solidified into formal specifications.