question-me

A Socratic spec analysis identifies hidden requirements by applying a structured interview protocol to your specification. It surfaces implicit assumptions and missing constraints through non-obvious questions, yielding a refined specification with clear tradeoffs before development begins.

Analyzing architecture assumptions is best achieved through a phase-based Socratic interview. This method breaks down spec review into Load, Interview, and Synthesis phases, systematically extracting unstated risk factors and documenting them for stakeholder alignment.

To start a Socratic interview for requirements analysis, initiate the process on your target spec file. The system automatically guides the first question cycle, asking 2-3 non-obvious questions at a time to elicit unstated assumptions before progressing to synthesis.

Socratic spec analysis produces a consolidated Markdown file named spec-refined.md. This output document captures all extracted decisions, tradeoffs, and open questions, providing a clear, actionable specification for stakeholders and developers.

Use Socratic requirements analysis when your spec is ambiguous or high-risk and you need to surface edge cases before coding. It enforces safety and anti-pattern checks to deliver a clear specification, preventing costly architectural rework later.