requirements-traceability

Build and maintain a requirements traceability matrix linking objectives, requirements, design, and tests.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-traceability-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-traceability
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/requirements-traceability
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-traceability-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose track of why requirements exist, whether every business objective is covered, and what breaks when a requirement changes. This Skill creates a bidirectional traceability matrix that answers coverage, impact, and audit questions systematically. ## Core Features & Use Cases - Traceability Matrix Construction: Link business objectives, user requirements, functional requirements, design elements, and test cases in both directions. - Coverage and Orphan Analysis: Detect requirements without sources (gold-plating), requirements without tests, and business objectives without implementation paths. - Impact Analysis: Trace forward and backward from any changed requirement to identify affected tests, designs, and dependent requirements. - Use Case: An auditor asks you to prove every requirement has a test case. Use this Skill to generate a full-chain matrix with coverage metrics and an orphan analysis showing exactly where gaps exist. ## Quick Start Create a requirements traceability matrix for my project linking business objectives, functional requirements, and test cases, then run a coverage analysis to find gaps.

Frequently Asked Questions about requirements-traceability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a requirements traceability matrix?▼

Start by deciding which artifacts to trace, minimally business objectives, functional requirements, and test cases. For each requirement, link backward to its source and forward to its test cases, then record status. Use the provided template to structure the matrix.

What is forward and backward traceability in requirements?▼

Forward traceability links business objectives to requirements to tests, confirming every need is implemented and verified. Backward traceability links requirements back to their sources, confirming nothing was gold-plated without a business justification.

How do I perform impact analysis when a requirement changes?▼

Locate the changed requirement in the matrix, trace forward to find affected test cases, trace backward to check alignment with business objectives, and trace laterally to dependent requirements. Document the full impact scope in the change request.

What are orphan requirements in a traceability matrix?▼

Orphan requirements have no backward trace to a business objective, suggesting gold-plating, or no forward trace to a test case, meaning they are unverified. The orphan analysis section of the matrix lists these gaps for corrective action.

When is a traceability matrix not worth maintaining?▼

A matrix loses value when it is created once and never updated as requirements change. Traceability updates must be a required step in the change control process, or the matrix becomes useless for impact analysis.