Requirements Validation Skill

Use When

independently reviewing drafted requirements for correctness, completeness, consistency, feasibility, traceability, and testability before baselining; use requirements-analysis to resolve raw elicitation conflicts.
Use this procedure when the required source artefacts are available and Validation findings and release recommendation is the next lifecycle deliverable.

Use requirements-analysis when that neighbouring route owns the decision or deliverable.
Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.

Artefact	Source or provider	Required?	Behaviour when missing
Draft requirements, source evidence, glossary, quality thresholds, and trace links	Requirements owner and independent reviewers	Yes	Stop the affected step, name the missing source, and return only a qualified gap record.