speckit.quizme

Evaluate specification documents with Socratic questioning for logical gaps and robustness issues.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/aniruddh2003/ai-code-reviewer --skill speckit-quizme-aniruddh2003
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.quizme
Source: https://github.com/aniruddh2003/ai-code-reviewer/tree/main/.agent/skills/speckit.quizme
Command: npx skills add https://github.com/aniruddh2003/ai-code-reviewer --skill speckit-quizme-aniruddh2003

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill challenges specification documents using Socratic questioning to uncover logical gaps, unhandled edge cases, and robustness issues.

Core Features & Use Cases

  • Socratic Questioning: Challenges specifications for logical fallacies, naive assumptions, and happy-path bias.
  • Edge Case Analysis: Identifies potential issues with temporal, state gaps, and business logic.
  • Security and Robustness: Assesses security concerns and "happy path" biases in system design.

Quick Start

Run 'quizme' to start the Socratic questioning process for a given spec.

Frequently Asked Questions about speckit.quizme

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find logical gaps and unhandled edge cases in my system specifications?

You can identify logical gaps in specifications by applying Socratic questioning to challenge naive assumptions and happy-path bias, probing missing definitions for business logic, security, and temporal states.

What is Socratic questioning for specification review and robustness evaluation?

Socratic questioning for specification review is a method that critically challenges documents by posing targeted questions to uncover logical fallacies, security vulnerabilities, and unhandled state or temporal gaps.

How do I analyze security concerns and temporal gaps in a specification document?

Analyze security and temporal gaps by probing the specification with critical questions that test business logic and robustness, systematically exposing potential pitfalls and missing state definitions.

Can I use Socratic questioning to evaluate business logic for happy path bias?

Yes, Socratic questioning evaluates business logic by actively challenging happy-path bias, exposing naive assumptions, and identifying unhandled edge cases within the specification document.

What are the limitations of using Socratic questioning for specification review?

Socratic specification review relies entirely on the quality of probing questions asked, meaning it may miss undocumented external dependencies or security flaws not explicitly referenced in the provided text.