Requirements Reuse Skill Guidance

Use When

curating approved reusable requirement patterns and product-line variants after a stable baseline exists; use requirements-patterns to structure one project's complex behaviour.
Use this procedure when the required source artefacts are available and Reusable requirements library is the next lifecycle deliverable.

Use requirements-patterns 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
Approved requirements, applicability context, variability rules, and provenance	Requirements baselines and product-line owner	Yes	Stop the affected step, name the missing source, and return only a qualified gap record.