discuss

Socratic dialogue helps clarify ambiguous product requirements by applying a structured DIAGNOSE, PROBE, and SYNTHESIZE flow. This method challenges assumptions, tests failure modes, and explores counter-arguments to turn vague ideas into refined discussion outcomes.

The best way to run an architecture review for a new idea is through a Socratic discussion that evaluates feasibility and tests assumptions. You can select specific probe directions like challenging assumptions or stress-testing edge cases to ensure robust architecture design.

Test assumptions during product discovery by engaging in a Socratic discussion that probes your initial ideas. By selecting probe directions that challenge assumptions and explore alternative paths, you surface hidden constraints and validate the core problem definition.

Yes, you can score the ambiguity of a feature idea by enabling an optional ambiguity scoring mode during the dialogue. This tracks an Ambiguity Score to help gauge when sufficient clarity is reached and drive toward a structured synthesis wrap-up.

Socratic discussion works for exploring codebase patterns during architecture design by using an optional deep mode context pull. This gathers concise existing codebase context first to ground the conversation in established patterns before probing assumptions.

You should avoid using Socratic dialogue for requirement discovery when you need to generate planning artifacts or implementation instructions. This approach enforces safe guardrails that focus strictly on problem definition and feasibility, avoiding actionable build plans.