spec-review

Review technical specification documents for ambiguities, gaps, and risks.

Updated Apr 26, 2026

Search Tags:#code-quality #technical-specification #requirements-analysis #spec-review #engineering-readiness

Ready to run

npx skills add https://github.com/ThanhNguyenDat/agent-skills --skill spec-review-thanhnguyendat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/ThanhNguyenDat/agent-skills/tree/main/spec-review
Command: npx skills add https://github.com/ThanhNguyenDat/agent-skills --skill spec-review-thanhnguyendat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents costly implementation errors by identifying ambiguities, missing requirements, and architectural risks in technical specifications before development starts.

Core Features & Use Cases

Implementation Readiness Assessment: Evaluates documents against 8 critical criteria including scope, data contracts, and error handling.
Iterative Feedback Loop: Supports re-reviewing updated drafts to ensure previous findings are resolved.
Use Case: Before starting a complex feature, use this skill to review your CLAUDE.md or PRD to ensure all edge cases and state transitions are clearly defined for the engineering team.

Quick Start

Use the spec-review skill to analyze the attached technical specification document for implementation readiness.

Frequently Asked Questions about spec-review

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

FAQPage Schema

How do I review a technical specification document for implementation readiness?▼

You validate implementation readiness by analyzing the technical specification against eight core criteria including business flow, data contracts, and security requirements to identify ambiguities, gaps, and risks prior to software development.

What is technical specification review and when do I need it?▼

Technical specification review is the process of validating feature specs, API contracts, and architectural design documents to ensure engineering readiness. You need it before starting implementation to prevent costly coding errors caused by missing requirements.

Can I use an iterative feedback loop to re-review an updated technical spec?▼

Yes, you can use an iterative feedback loop to re-review updated technical specification drafts. This process ensures that previous findings regarding ambiguities, missing requirements, and architectural risks are fully resolved before development starts.

Does technical specification validation work for API contracts and architectural design documents?▼

Technical specification validation works effectively for API contracts and architectural design documents. It evaluates content against eight core criteria including data contracts and security requirements to ensure full engineering readiness.

What is the best way to identify missing requirements in a PRD before coding?▼

The best way to identify missing requirements in a PRD before coding is to validate the document against eight core criteria including business flow, data contracts, and error handling to pinpoint ambiguities and architectural risks.

What limitations exist when analyzing a CLAUDE.md file for edge cases and state transitions?▼

When analyzing a CLAUDE.md file for edge cases and state transitions, limitations depend on the content clarity within the technical specification. The review strictly validates existing document text against eight criteria rather than generating missing architectural designs.