spec-validator

Cross-checks Datasheet, Application Note, and Spec documents for consistency and quality scores.

26|8|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/vibeic/vibe-ic --skill spec-validator-vibeic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-validator
Source: https://github.com/vibeic/vibe-ic/tree/main/vibe-ic-marketplace/plugins/vibe-ic/skills/spec-validator
Command: npx skills add https://github.com/vibeic/vibe-ic --skill spec-validator-vibeic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? IC design documents generated in Phase 1 (Datasheet, Application Note, Spec) often contain inconsistencies such as pin name mismatches, register address conflicts, and unresolved TBD placeholders that silently propagate into RTL. This Skill runs deterministic scoring and cross-document checks so these defects are caught before the Phase 1 to Phase 2 checkpoint gate. ## Core Features & Use Cases - Datasheet Quality Scoring: Scores a Markdown datasheet on 10 criteria (0-100) with a Checkpoint 1 threshold of 70 via ds_quality_check.py. - Application Note Scoring: Scores an application note on 8 criteria (0-80) with a threshold of 56 via an_validator.py. - Cross-Document Consistency: Detects pin-mismatch, register-mismatch, and unresolved-tbd errors between DS, AN, and Spec via spec_validator.py, plus a spec-to-RTL conformance gate once RTL exists. - Use Case: Before advancing a sensor IC from Phase 1 to Phase 2, run all checks on the project directory; if the AN firmware example references a register missing from the DS register map, the check reports an ERROR and blocks the gate until fixed. ## Quick Start Ask the AI to run the spec validator on the current project directory to cross-check the datasheet and application note before the Phase 1 to Phase 2 checkpoint gate.

Frequently Asked Questions about spec-validator

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

FAQPage Schema
How do I check consistency between a datasheet and application note?▼

Run spec_validator.py with the datasheet and application note paths, or point it at the project directory to auto-locate both files. It cross-checks pin names, register addresses, and TBD placeholders, reporting ERROR-level mismatches that must reach zero before the checkpoint gate.

What quality score does a datasheet need to pass Checkpoint 1?▼

The datasheet must score at least 70 out of 100 across 10 criteria including pin configuration, electrical characteristics, and timing diagrams. The application note must score at least 56 out of 80 across 8 criteria.

Does the spec validator work when a document section is missing?▼

Yes. Checks degrade to MISSING or SKIP rather than false failures when a file or section is absent. A missing datasheet returns exit code 2, treated as not yet produced rather than a failure.

Can the validator check that RTL matches the specification?▼

Yes, spec_conformance_check.py extracts the expected interface, reset semantics, and latency from the spec and diffs them against the RTL. It reports port mismatches and reset-mode conflicts as ERRORs, requiring zero errors to pass.

What are the limitations of the cross-document consistency check?▼

The cross-check performs structural string comparison only and does not detect semantic inconsistencies, such as understanding that SCL is the I2C clock. It is also less suited to complex SoC datasheets whose structure differs from discrete IC templates.