When any system requirements activity is required.
Critical Patterns
Shall strictly follow the provided resources and recursively review all referenced documents required to understand the current process, inputs, outputs, rules and directly referenced work products.
Shall align with specifications (no inconsistencies).
Shall ensure all system requirements are derived from specifications by adding explicit traceability between them.
Shall avoid embedding architectural or implementation decisions in system requirements.
Shall keep documentation DRY (Don't Repeat Yourself) by adding references instead of duplicating content.
Shall ask for approval when system requirements are incomplete, ambiguous, or conflicting.
Shall request final validation before closing the system requirements to ensure no further iterations are needed.
Resources
Documentation: See for resources needed to perform this skill.