spec/review

Extract terms and verify references in technical specification documents.

5|3|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/NexusSema/omg-marketplace --skill spec-review-nexussema
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec/review
Source: https://github.com/NexusSema/omg-marketplace/tree/main/plugins/sdlc/skills/spec/review
Command: npx skills add https://github.com/NexusSema/omg-marketplace --skill spec-review-nexussema

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a systematic approach to analyzing technical specifications, ensuring terminology is captured, references are valid, and content remains free of contamination or inconsistencies.

Core Features & Use Cases

  • Term Registry building from headers, bold terms, code identifiers, and glossary entries.
  • Consistency & Cross-Reference checks to detect synonyms, conflicting definitions, and broken links.
  • Contamination & Structure scanning to flag non-spec artifacts and verify document organization.
  • Use Case: Teams can run spec-review on PRs or design documents to generate a compliance report that guides editorial improvements.

Quick Start

Run spec-review on your technical documents to produce a structured quality report.

Frequently Asked Questions about spec/review

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

FAQPage Schema
How do I check technical specifications for term consistency and broken references?▼

To check technical specifications for term consistency, you can audit documents to build a term registry from headers, bold terms, and glossaries, verifying cross-reference validity and flagging inconsistencies automatically.

What is a term registry and how does it help with documentation quality assurance?▼

A term registry is a catalog of terms extracted from headers, bold text, code identifiers, and tables. It helps documentation quality assurance by detecting conflicting definitions, synonyms, and structural inconsistencies across technical specs.

How do I scan technical documents for non-spec content and contamination patterns?▼

To scan technical documents for non-spec content and contamination patterns, apply an automated audit that identifies structural elements, verifies document organization, and flags artifacts that do not belong in specifications.

Can I run spec reviews on pull requests to ensure design document compliance?▼

Yes, you can run spec reviews on pull requests to ensure design document compliance. The process analyzes terminology and cross-references to generate a structured quality report that guides editorial improvements.

What is the best way to extract defined terms from headers, tables, and glossary entries?▼

The best way to extract defined terms from headers, tables, and glossary entries is to apply a systematic extraction process that catalogs code identifiers and text elements into a robust term registry for consistency checks.