techspec-validator

You can validate PRD-to-TechSpec mapping by running the validator against your current documents. It checks file paths, interfaces, breaking changes, and dependencies, then generates a techspec-validation.md report highlighting coverage gaps and remediation steps.

TechSpec validation is the process of ensuring all PRD requirements have corresponding technical coverage. It is needed before task generation to detect gaps, prevent project blockers, and verify internal consistency across the codebase and TechSpec document.

To check for breaking changes and interface consistency, the validator applies validation rules directly against the TechSpec document and codebase. It identifies discrepancies and outputs warnings in the generated techspec-validation.md report to guide remediation.

No external dependencies or components are required. The skill operates independently to analyze file paths, internal consistency, and PRD-to-TechSpec coverage within your existing environment.

The best way to report blockers is to generate a techspec-validation.md file. This report surfaces validation gaps, details broken dependencies, and provides explicit remediation steps for uncovered PRD requirements.

You should worry when file paths referenced in the document do not exist in the codebase, or when PRD requirements lack corresponding implementation details. These internal consistency failures create immediate project blockers that the validation report highlights.