speckit.quizme

Socratic red-teaming finds edge cases missing from your software requirements spec by challenging happy-path assumptions through guided dialogue. This approach surfaces logical fallacies, race conditions, and undefined constraints, capturing each resolved scenario as a new requirement for spec.md.

Socratic red-teaming for spec analysis is a questioning technique that exposes gaps in feature specifications. It challenges scenarios where happy-path assumptions fail and constraints are undefined, ensuring quality assurance by iteratively refining the specification with newly discovered edge cases.

Run a spec analysis quiz by loading spec.md and plan.md, then beginning the guided 3-5 scenario challenge loop. The quiz presents edge-case scenarios and critique prompts, allowing you to resolve gaps and propose the newly articulated requirements for integration into spec.md.

Yes, you can use Socratic questioning to find race conditions in your spec. The red-teaming dialogue specifically targets logical fallacies and race conditions by probing scenarios where initial spec assumptions fail and undefined edge cases exist.

Limitations of using Socratic dialogue for quality assurance include its reliance on a guided quiz loop of only 3-5 edge-case scenarios per session. It requires existing spec.md and plan.md files to function and focuses strictly on undefined constraints rather than generating new core features.