Analyze specification documents for gaps, ambiguities, and edge cases.
npx skills add https://github.com/JDenn0514/surveycore --skill spec-reviewer
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
Adversarially review a specification document to identify gaps, ambiguities, under-specifications, and missing edge cases before coding starts, reducing rework and defects.
Paste the spec text you want reviewed and command the system to perform a comprehensive adversarial review.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
onejaejaeGenerate a 7-section specification document from structured requirements.
JotJuniorIdentify and resolve spec ambiguities through structured questions and update the document.
patricio0312revGenerate API test suites from route definitions for Express, Next.js, and Fastify.
phatblatStress-test ideas against 11 persistent world models across multiple time horizons.
