Requirements Traceability Matrix

Skill files

The public post is only the explanation. Use these links to inspect or download the actual reviewed skill artifact.

skill.mdDownload SKILL.mdevalDownload evals.json

Skill Overview

Requirements traceability is valuable because it keeps delivery teams from building orphaned features, missing compliance needs, or treating vague stakeholder wishes as test-ready requirements. The requirements-traceability-matrix Codex skill gives Business Analysts a repeatable way to convert discovery notes, BRDs, Jira stories, workshop notes, compliance requirements, and QA notes into a matrix that is ready for product, engineering, QA, compliance, or implementation review.

The skill is intentionally narrow. It does not try to perform the entire BA role or replace stakeholder judgment. It focuses on one concrete workflow: building a traceability package that shows where each requirement came from, what business objective it supports, how it will be validated, who owns it, and what remains unresolved before sign-off.

Intended Role

This skill is designed for Business Analysts preparing requirements for product, engineering, QA, compliance, business operations, or implementation teams. It is especially useful before sprint planning, UAT readiness review, regulatory review, vendor handoff, or stakeholder sign-off.

Required Inputs

• Source material such as stakeholder interview notes, workshop notes, BRDs, FRDs, epics, user stories, Jira exports, process notes, compliance requirements, test scenarios, defect notes, or change requests.
• Project context such as product area, release, process, customer segment, regulation, decision deadline, current scope, known constraints, or delivery phase when available.
• Stakeholder context such as requester, approver, product owner, engineering owner, QA owner, compliance owner, support owner, or affected business unit when available.
• Desired output audience, such as product, engineering, QA, compliance, implementation partner, steering committee, or business sign-off group.

The skill can proceed with incomplete notes, but it labels missing evidence instead of filling gaps with false certainty.

Expected Output

The skill produces:

• Scope summary with project, source inputs, audience, traceability goal, and readiness status.
• Requirements traceability matrix with IDs, sources, objectives, requirement statements, requirement types, priorities, owners, acceptance criteria, validation coverage, dependencies, statuses, and gaps.
• Gap and ambiguity log for missing evidence, unclear terms, conflicting requests, unowned requirements, and validation gaps.
• Conflict and change-impact notes for duplicated, competing, or downstream-impacting requirements.
• Sign-off readiness assessment tied to the evidence in the matrix.
• Follow-up questions grouped by stakeholder or owner.
• Paste-ready handoff note for delivery, QA, compliance, or stakeholder review.

Validation Scenario

The included eval set checks three realistic Business Analyst situations:

• A loan origination workflow update with compliance audit needs, document-upload rules, notification privacy questions, classification-confidence risk, and missing QA coverage.
• A procurement approval redesign with threshold routing, category approvals, SaaS security review, legal review, NetSuite sync, Slack notifications, and a renewal-routing conflict.
• An employee benefits enrollment UAT review with country-specific eligibility rules, policy gaps, accessibility validation, non-US QA coverage gaps, and analytics ownership questions.

The expected outputs verify that the skill creates linked requirements, separates objectives from detailed requirements, flags ambiguous or conflicting scope, gives honest validation coverage, identifies missing owners, and assesses sign-off readiness without overstating certainty.

Operational Limits

This is a low-risk workflow skill for preparing structured analysis material. It does not access private systems by itself, update Jira or test-management tools, approve requirements, interpret legal obligations, replace compliance review, or make release decisions.

Business Analysts should review the matrix with the appropriate product, engineering, QA, legal, compliance, security, accessibility, and business owners before using it for approval, build, vendor handoff, or audit evidence.

Maintenance Expectations

Review this skill when the team’s requirement taxonomy, delivery workflow, sign-off process, test-management approach, regulatory environment, or ownership model changes. Refresh evals when new recurring BA scenarios appear, such as AI governance requirements, data-retention reviews, vendor integration mapping, accessibility exceptions, or regulated audit trails.

Related Existing Skills

These public skills and skill libraries are adjacent to Business Analyst traceability work. The closest public resources found were broader BA skills and one BA skill pack with a traceability starter; no close public match focused only on turning messy source notes into a sign-off-ready requirements traceability matrix with gaps, validation coverage, and owner follow-ups.

• Technical Business Analyst: a broader agent skill for technical research, requirements extraction, effort estimation, risk assessment, and planning. The airoweb skill stays narrower by focusing on traceability and sign-off readiness rather than discovery planning or technology trade-off analysis.
• business-analysis-skills: a platform-neutral BA skill pack with many atomic techniques and workflows, including a requirements-traceability-starter. This is the closest adjacent public resource found; the airoweb skill packages the traceability workflow as one operational Codex skill with eval scenarios and a defined output package.
• Business Analyst Agent: a compact general-purpose Business Analyst agent covering requirements gathering, process improvement, stakeholder management, and solution design. It is useful role context, but broader and less prescriptive about RTM outputs.
• business-analyst: a marketplace listing for a broad BA skill that mentions requirements traceability and validation among many BA practices. The airoweb skill turns that one activity into a concrete repeatable workflow.
• The IT Business Analyst Skill for Claude: an article describing a wider BA toolkit for requirements documentation, user stories, process mapping, stakeholder communication, and traceability. It is a useful comparison point for scope, while the airoweb artifact is smaller and easier to evaluate.