Requirements Metrics & Quality Gates Skill Guidance

Use When

measuring requirement quality and enforcing quantitative gates for ambiguity, completeness, traceability, volatility, and testability; use requirements-validation for content review.
Use this procedure when the required source artefacts are available and Requirements quality scorecard is the next lifecycle deliverable.

Use requirements-validation 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
Requirements baseline, metric definitions, thresholds, and prior results	Requirements owner and quality standards	Yes	Stop the affected step, name the missing source, and return only a qualified gap record.