spec-review

Analyze specification documents and generate a structured issue log.

346|50|Updated Jan 17, 2026

Search Tags:#documentation #consistency #ambiguity #reporting #gap-analysis #spec-review #issue-log

Ready to run

npx skills add https://github.com/liza-mas/liza --skill spec-review-liza-mas

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify inconsistencies, gaps, and ambiguities in specification documents to improve quality and reduce rework.

Core Features & Use Cases

Corpus discovery and classification: maps and prioritizes documents as primary specs vs references.
Issue-driven analysis: logs issues with location, type, severity, description, and remediation suggestions.
Systematic checks: performs cross-document consistency, completeness, and error-handling validations to ensure readiness for implementation.

Quick Start

Upload or point to your specification corpus (e.g., specs/ or docs/). Run the spec-review skill to generate a structured report outlining found issues and suggested fixes.

Frequently Asked Questions about spec-review

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

FAQPage Schema

How do I find inconsistencies and gaps in specification documents before coding?▼

To find inconsistencies and gaps in specification documents, you can run an automated spec review that analyzes your entire corpus, classifies primary specs versus reference material, and generates an audit-ready issue log with severity and remediation suggestions.

What is the best way to perform a cross-document consistency check for technical specifications?▼

The best way to perform a cross-document consistency check is to systematically validate completeness and error-handling logic across mapped relationships within the specification corpus, producing a structured report of identified ambiguities.

How do I generate an issue log for specification ambiguities and missing requirements?▼

You can generate an issue log for specification ambiguities by analyzing the targeted subdirectories of your documentation, mapping document relationships, and extracting issues categorized by location, type, severity, description, and suggested fixes.

Can I analyze a large corpus of mixed documentation and reference materials for spec readiness?▼

Yes, you can analyze a large mixed corpus for spec readiness by mapping and prioritizing documents into primary specs and references, then performing systematic checks to validate completeness and error-handling for implementation.

How do I structure a specification gap analysis report for development teams?▼

To structure a specification gap analysis report, document each found issue with its exact location, type, severity, description, and remediation suggestions to ensure the output is structured and audit-ready for the development team.

Why should I review specification documents for ambiguities before starting implementation?▼

You should review specification documents for ambiguities before implementation to improve overall document quality, identify missing requirements early, and significantly reduce costly rework during the coding phase.