{
  "skill_name": "requirements-traceability-matrix",
  "evals": [
    {
      "id": 1,
      "prompt": "I am the BA for a loan origination workflow update. Build a requirements traceability matrix from these notes for product, engineering, QA, and compliance. Business goal: reduce manual rework when applicants upload incomplete documents. Compliance needs an auditable reason whenever an application is returned to the applicant. Product wants this in the Q3 broker portal release. Notes: brokers can upload bank statements, pay stubs, IDs, and tax returns; system should flag missing required document types before submission; underwriters want to override the flag with a reason; applicants should receive a notification listing missing documents; QA only has a happy-path test for a complete application; security asked whether PII is shown in notification emails; engineering says document classification confidence can be below 90% for scans; no one has defined the SLA for document check time.",
      "expected_output": "A traceability package with linked business objectives, normalized functional/non-functional/business-rule/data requirements, partial or missing QA coverage, compliance and PII gaps, document-classification confidence risk, sign-off readiness assessment, and targeted follow-up questions."
    },
    {
      "id": 2,
      "prompt": "Turn this discovery dump into an RTM. Context: internal procurement approval redesign. CFO objective is to cut off-contract spend by requiring approval before purchase orders over $25k. Procurement wants category managers to approve software and hardware requests. IT says security review is mandatory for SaaS vendors. Legal says contracts over 3 years need legal review. Requesters want Slack notifications. Finance ops says approvals must sync to NetSuite every 30 minutes. There is a Jira story for PO threshold routing but nothing for SaaS security review. QA has draft tests for $25k routing and NetSuite sync only. The workshop notes disagree on whether renewals follow the same route as new purchases.",
      "expected_output": "A Business Analyst RTM that separates business rules, workflow requirements, integration and notification requirements, maps each to the CFO/procurement/security/legal objectives, flags the renewal-routing conflict, identifies missing Jira and QA coverage, and assesses sign-off readiness."
    },
    {
      "id": 3,
      "prompt": "Please prepare a traceability matrix from these stakeholder notes before tomorrow's UAT readiness review. Product area: employee benefits enrollment. HR goal: reduce open-enrollment support tickets by giving employees clearer dependent eligibility messages. Notes: employees can add spouse, domestic partner, child, or stepchild; eligibility depends on country and plan type; legal provided a policy PDF but I only pasted the summary here; engineering says country and plan type are already in Workday; support wants a printable confirmation page; accessibility lead says error messages need to meet WCAG guidance; QA has tests for US employees only; HR operations wants reports of ineligible dependent attempts by country; no owner is listed for analytics.",
      "expected_output": "A UAT-focused requirements traceability package with business objective linkage, functional and non-functional requirements, policy and analytics gaps, QA coverage limitations for non-US cases, accessibility validation needs, owner gaps, and a readiness recommendation."
    }
  ]
}