spec-reviewer

Analyze specification documents for gaps, ambiguities, and edge cases.

1|Updated Feb 17, 2026

Search Tags:#edge-cases #gaps #risk-analysis #test-cases #adversarial-review #ambiguities #spec-review

Ready to run

npx skills add https://github.com/JDenn0514/surveycore --skill spec-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-reviewer
Source: https://github.com/JDenn0514/surveycore/tree/main/.claude/skills/spec-reviewer
Command: npx skills add https://github.com/JDenn0514/surveycore --skill spec-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarially review a specification document to identify gaps, ambiguities, under-specifications, and missing edge cases before coding starts, reducing rework and defects.

Core Features & Use Cases

Section-by-section critique across the entire spec using structured lenses to surface hidden assumptions and failure modes.
Structured issue reports that categorize problems by severity and provide actionable recommendations for resolution.
Phase-agnostic workflow for early risk assessment, with guidance on test coverage and contract completeness.

Quick Start

Paste the spec text you want reviewed and command the system to perform a comprehensive adversarial review.

Frequently Asked Questions about spec-reviewer

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

FAQPage Schema

How do I identify gaps and ambiguities in a software specification before coding starts?▼

To identify gaps and ambiguities in a software specification, you perform an adversarial spec review that analyzes the document section-by-section using structured lenses to surface hidden assumptions. This process generates a categorized issue report highlighting under-specifications and missing edge cases.

What are the best ways to find missing edge cases and under-tested areas in a spec document?▼

The best way to find missing edge cases and under-tested areas in a spec document is by applying the Five Review Lenses, which include Test Completeness and Edge Cases analysis. This structured critique evaluates the specification to ensure comprehensive test coverage and contract completeness.

How do I run an adversarial review on a specification document?▼

To run an adversarial review on a specification document, paste the spec text into the system and command a comprehensive review. The system consumes the text and evaluates it against five lenses: DRY, Test Completeness, Contract Completeness, Edge Cases, and Engineering Level.

Does this spec review process work for early risk assessment before any code is written?▼

Yes, this spec review process works for early risk assessment before any code is written because it is phase-agnostic. It adversarially surfaces under-specifications and missing edge cases early, reducing rework and defects by providing actionable recommendations for resolution.

What format does the structured critique report use for spec issues?▼

The structured critique report outputs a formatted issue list that categorizes spec problems by severity. It provides actionable recommendations for resolution and generates a saved plan to guide the mitigation of identified ambiguities and gaps.

When should I not use an adversarial spec review?▼

You should not use an adversarial spec review for multi-document cross-referencing, as it is designed for single-spec reviews only. It targets section-by-section analysis of one document rather than evaluating relationships across multiple specification files.