Requirements Management Skill Guidance

Use When

baselining requirements and controlling changes, versions, decisions, and impact after requirements exist; use requirements-validation before accepting content into a baseline.
Use this procedure when the required source artefacts are available and Requirements baseline and change-control record 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
Validated requirements set, change policy, owners, and repository history	Requirements owner and governance records	Yes	Stop the affected step, name the missing source, and return only a qualified gap record.