validate-requirements

Validate requirements by analyzing your requirements documentation to enforce unique REQ-* keys, correct formatting, acceptance criteria presence, testability, traceability, and clear language. This skill identifies defects and provides actionable suggestions to prevent rework and miscommunication before design begins.

Testable requirements have measurable acceptance criteria with clear pass/fail conditions. Traceable requirements link back to their original intent or user need. This skill checks both properties, flagging ambiguous language and missing traceability that block implementation.

Yes. This skill acts as a quality gate that blocks progression to the Design stage if critical requirement issues are detected, ensuring all requirements are clear, testable, and traceable before downstream work begins.

The skill validates unique keys, key format compliance, acceptance criteria existence, criterion testability, traceability to intent, and removal of ambiguous language across all requirements in your docs/requirements/ directory.

Vague, untestable, or incomplete requirements cause miscommunication between teams, rework during implementation, and wasted effort in later stages. Validation catches these defects early before they propagate to design and development.