deep-interview

To clarify vague project requirements before automation, you can conduct a Socratic interview that asks one question at a time, using ambiguity scoring to surface hidden assumptions and yield a precise, actionable spec.

Socratic ambiguity gating is a disciplined interview process that extracts ontology and tracks domain model stability, ensuring a project spec converges only when mathematical ambiguity is sufficiently reduced.

To extract an ontology from a greenfield project idea, engage in a guided interview that identifies domain concepts and tracks their stability, progressively refining the model until a stable domain representation is achieved.

Yes, you can use this structured interview process for brownfield enhancements; it is explicitly designed to reduce risk by clarifying requirements for both new greenfield ideas and updates to existing brownfield systems.

Crystallized specs are saved as detailed markdown files to a designated disk path, providing auditability and creating a formal bridge for handoff to downstream planning and execution pipelines.

The best way to reduce project risk before autonomous execution is to apply mathematical ambiguity gating through a deep interview, ensuring all hidden assumptions are surfaced and resolved before implementation begins.