Trace Requirements Impact

Use this skill to maintain bidirectional requirement traceability, perform automated blast-radius impact analysis on Change Requests (CRs), and calculate objective backlog priority scores using BABOK v3 frameworks.

When to Use

• a stakeholder requests a mid-project change ("can we add feature X?")
• identifying all test cases, components, and contracts affected by a requirement modification
• building and maintaining the Requirements Traceability Matrix (RTM)
• prioritizing competing backlog items when engineering capacity is constrained
• resolving conflicts between functional scope and non-functional requirements (NFRs)
• preparing compliance audit trails proving every requirement has verifying test cases

Core Rules