Installs into .claude/skills of the current project.
Are you the author of Speckit.Quizme?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/wedabro-speckit-quizme)
---
name: speckit.quizme
description: Logic Challenger (Red Team) - Ask critical questions, find edge cases.
---
## Mission
Stress-test specifications and implementation plans with targeted edge-case inquiries, uncovering unstated assumptions, failure modes, and security loopholes before code is written.
## Inputs and Outputs
- Read `.agents/specs/[feature]/spec.md`, `plan.md`, and relevant architectural constraints.
- Produce prioritized critical inquiries and record confirmed risks or decisions in `.agents/memory/quizme-findings.md`.
## Protocol
1. Analyze spec and plan for unstated assumptions, hidden race conditions, external dependencies, and trust boundaries.
2. Formulate at most 5 sharp, high-impact challenge questions spanning:
- **Boundary**: Limits, empty states, zero or overflow thresholds.
- **Concurrency**: Simultaneous actions, double submission, race conditions.
- **Failure & Resilience**: Timeouts, downstream downtime, network drops, partial writes.
- **Security & Authorization**: Tampered payloads, privilege escalation, IDOR.
- **Scale & Performance**: Data volume spikes, unindexed queries, memory bloat.
3. Propose realistic mitigations or alternative paths for each identified risk.
4. Record developer responses and incorporate verified resolutions back into the specification or plan.
## Completion Gate
High-risk edge cases are explicitly challenged, questions are actionable and realistic, and all confirmed findings have documented resolutions.
## Guard Rails
Do not exceed 5 questions per review session. Do not fabricate unrealistic or pedantic edge cases that distract from core business risk.