specification-validation

Specification validation checks PRD, SDD, and PLAN documents against the 3Cs framework—completeness, consistency, and correctness. Run validation by referencing document sections to ensure requirements are fully defined, internally aligned, and technically sound before implementation begins.

Ambiguity detection identifies vague language and unclear specifications across PRD and SDD artifacts. The Skill flags problematic phrasing and proposes clarifications to eliminate misinterpretation and ensure all stakeholders share a common understanding.

Cross-document comparison validates traceability across PRD, SDD, PLAN, and related code artifacts. This mode ensures requirements flow consistently through design and planning phases into implementation, catching disconnects early.

Understanding validation assesses whether specifications, implementations, and team understanding align. Apply the 3Cs framework to code and artifacts to confirm that what was built matches what was specified and intended.

Specification mode validates PRD, SDD, and PLAN document quality directly. File validation mode checks individual artifacts for internal consistency and completeness; comparison mode cross-references multiple documents for alignment.

Run validation as a pre-implementation check after requirements and design documents are drafted. Early validation catches inconsistencies and ambiguities before development begins, reducing rework and miscommunication downstream.