specification_validation

Validates software specifications for completeness, consistency, and implementation alignment.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill specification-validation-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specification_validation
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/specification_validation
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill specification-validation-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Software specifications often contain missing requirements, ambiguous wording, conflicting definitions, and gaps between documented behavior and actual code, leading to rework and defects. This Skill provides a structured framework to audit specs before and during development. ## Core Features & Use Cases - Completeness Check: Verify that specs include functional requirements, non-functional requirements, edge cases, error handling, and acceptance criteria using a structured template. - Consistency & Conflict Detection: Cross-reference UI specs, API specs, database schemas, and test specs to find contradictions such as mismatched field constraints. - Implementation Comparison: Compare spec-defined endpoints and features against the actual codebase to track implementation and test coverage status. - Use Case: Before a sprint starts, run a validation pass on a feature spec to catch TBD placeholders, ambiguous terms like "fast", and missing error-handling sections, then produce a gap report for stakeholders. ## Quick Start Validate the attached feature specification for completeness, ambiguity, and consistency with the current API implementation.

Frequently Asked Questions about specification_validation

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

FAQPage Schema
How do I validate a software specification document?

Validate a specification by checking completeness of required sections, auditing for ambiguous terms, detecting conflicts between business rules, and verifying traceability from requirements to test cases. This Skill provides checklists for each validation dimension.

How to compare a specification against actual code implementation?

Extract defined endpoints or features from the spec document, then grep the codebase for corresponding implementations such as route annotations, and diff the two lists. Track each feature in a status matrix covering spec, implementation, and test columns.

What should a complete software specification include?

A complete spec includes an overview with goals and success metrics, functional requirements with use cases and business rules, non-functional requirements for performance and security, technical details like API contracts and data models, and edge cases with error handling.

How do I detect inconsistencies between API and UI specifications?

Build a cross-reference matrix mapping each requirement across UI spec, API spec, database schema, and test spec. Flag mismatches such as differing field length limits, then document each conflict with an ID, location, description, and resolution.

What are common signs of a low-quality requirements document?

Warning signs include leftover TBD placeholders, ambiguous words like fast or user-friendly without measurable criteria, inconsistent terminology for the same concept, missing stakeholder approval, and requirements lacking priority ratings or test coverage.