specification-validation

Validate specifications and implementations for completeness, consistency, and correctness.

Updated Dec 28, 2025

Search Tags:#documentation #validation #specifications #traceability #quality-assurance #cross-document

Ready to run

npx skills add https://github.com/I2olanD/dotfiles --skill specification-validation-i2oland

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specification-validation
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/specification-validation
Command: npx skills add https://github.com/I2olanD/dotfiles --skill specification-validation-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to validating specifications, implementations, and understanding for completeness, consistency, and correctness. It helps teams ensure alignment across PRDs, SDDs, PLANs, and implementations, reducing ambiguity and rework.

Core Features & Use Cases

Mode A: Specification Validation — assesses PRD/SDD/PLAN quality and cross-document alignment.
Mode B: File Validation — checks individual files for structure, markers, and completeness.
Mode C: Comparison Validation — traces requirements from specs to implementations and reports deviations.
Mode D: Understanding Validation — evaluates the correctness of approach or design decisions.
Automated checks: basic content presence, cross-reference validation, ADR status, and traceability.

Quick Start

To start using the Specification Validation Skill, run your standard validation workflow against the target documents and let the tool propose improvements for completeness, consistency, and correctness.

Frequently Asked Questions about specification-validation

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

FAQPage Schema

How do I validate specifications for completeness and consistency across project artifacts?▼

Specification validation assesses PRDs, SDDs, and PLANs for completeness, consistency, and correctness through cross-document alignment and traceability checks. It applies a lightweight, advisory approach across modes A-D to reduce ambiguity and rework.

What is cross-document traceability in specification validation?▼

Cross-document traceability tracks requirements from specifications to implementations to report deviations. It enforces basic content presence and cross-reference validation across PRDs, SDDs, and PLANs to ensure project artifacts remain aligned.

How do I check if my PRD and SDD are aligned?▼

Mode A specification validation assesses PRD and SDD quality by checking cross-document alignment, automated content presence, and ADR status. This ensures your design decisions and requirements are structurally consistent across artifacts.

Can I trace requirements from specs to implementations without external tooling?▼

Yes, specification validation requires no external tooling beyond local file access. Mode C comparison validation traces requirements from specs to implementations and reports deviations using a lightweight, advisory approach with optional artifacts.

How do I validate the correctness of design decisions in my project?▼

Mode D understanding validation evaluates the correctness of your approach or design decisions. It provides advisory readiness checks across project artifacts to ensure your technical decisions align with specification requirements.

What are the limitations of using a lightweight advisory approach for specification validation?▼

The lightweight, advisory approach supports optional artifacts and local file access but does not enforce rigid compliance. It focuses on proposing improvements for completeness, consistency, and correctness rather than automatically fixing specification deviations.