spec-review

Analyze specification corpora for inconsistencies, gaps, and ambiguities.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Abkr1/liza --skill spec-review-abkr1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/Abkr1/liza/tree/main/skills/spec-review
Command: npx skills add https://github.com/Abkr1/liza --skill spec-review-abkr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec review helps teams detect inconsistencies, gaps, contradictions, and ambiguities within technical specifications, preventing misinterpretations during implementation and reducing downstream rework.

Core Features & Use Cases

  • Corpus discovery and classification across specs, ADRs, and design documents.
  • Cross-document consistency checks for term usage, state names, and cross-references.
  • Gap and ambiguity detection with prioritized issue reporting.
  • Phase-based analysis with traceable locations, severities, and recommendations.
  • Generates actionable reports for product and engineering teams to improve documentation quality.

Quick Start

Invoke the spec-review workflow on your specifications directory (e.g., specs/ or docs/) to produce a structured report. Review the highest-severity issues first and implement recommended changes.

Frequently Asked Questions about spec-review

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

FAQPage Schema
How do I detect inconsistencies and gaps across multiple technical specifications?▼

To detect inconsistencies and gaps across technical specifications, you can run a spec review workflow that cross-references documents to identify ambiguities and report prioritized issues with severities and locations.

What is cross-document consistency checking for technical specs?▼

Cross-document consistency checking analyzes a specification corpus to verify term usage, state names, and cross-references across multiple documents, ensuring documentation coherence and preventing misinterpretations during implementation.

How do I perform a phase-based analysis on a design document repository?▼

Perform phase-based analysis on a repository by invoking a spec review workflow that classifies specs, ADRs, and design documents, then applies targeted checks to determine coverage and coherence for specific subsystems.

Do I need external tools or dependencies to audit specification quality?▼

You do not need external tools or dependencies to audit specification quality, as the analysis requires only the provided repository files to generate a structured issue list with locations, types, and recommendations.

What is the best way to generate actionable reports for documentation ambiguity detection?▼

The best way to generate actionable reports for documentation ambiguity detection is using an automated spec review process that outputs a structured list highlighting traceable locations, issue severities, and recommended changes.

When should I use an automated spec review instead of manual documentation checks?▼

You should use automated spec review instead of manual checks when validating a large specification corpus, as it systematically cross-references terms and applies phase-based analysis to find gaps that manual reviews often miss.