What is the output format of the validation report?

It generates a structured Markdown report summarizing total items checked, passed items, and detailed discrepancy logs with recommended fixes.

Which specific documents does this skill analyze?

It targets Screen Definitions, Database Definitions, Project Plans, and API Contracts, primarily located in the docs/ and docs/mvp/ directories.

How does the skill handle terminology mismatches?

It scans all documents for inconsistent naming of Screen IDs, Table/Field names, and Function titles, flagging them in a 'Terminology' report.

Can I run checks for specific document pairs only?

Yes, you can use flags like /validate-docs --check screen-db or --check api to focus on specific areas of your documentation.

Document Integrity Validator

Name: Document Integrity Validator
Author: jskjw157

byjskjw157

Learning & Documentation

Ensures consistency and structural alignment between project requirements, UI definitions, database schemas, and API contracts.

About

The validate-docs skill automates the critical task of cross-referencing project documentation to ensure technical consistency across the development lifecycle. It analyzes screen definitions, database schemas, project plans, and API contracts to identify missing data fields, unimplemented features, or terminology mismatches. By generating comprehensive discrepancy reports with actionable advice, it prevents architectural drift and ensures that the implementation stays perfectly aligned with the original planning documents.

Key Features

Automated reporting with severity levels and recommended corrective actions
Cross-document mapping between UI screens and database tables
API-to-Database field consistency and naming verification
0 GitHub stars
Unified terminology checks for standardized naming across the repository
Functional coverage analysis comparing project plans to implementation docs

Use Cases

Verifying documentation integrity after major UI or database schema updates
Auditing technical specifications before development to ensure API support for all screens
Synchronizing legacy documentation with current MVP requirements during project reviews

About

Key Features

Automated reporting with severity levels and recommended corrective actions
Cross-document mapping between UI screens and database tables
API-to-Database field consistency and naming verification
0 GitHub stars
Unified terminology checks for standardized naming across the repository
Functional coverage analysis comparing project plans to implementation docs

Use Cases

Verifying documentation integrity after major UI or database schema updates
Auditing technical specifications before development to ensure API support for all screens
Synchronizing legacy documentation with current MVP requirements during project reviews