traceability-matrix

Generate traceability matrices mapping goals to deployed artifacts with typed links.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill traceability-matrix-ssiertsema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traceability-matrix
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/traceability-matrix/skills/traceability-matrix
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill traceability-matrix-ssiertsema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The traceability-matrix skill creates a comprehensive linkage across goals, requirements, stories, tests, and deployed artifacts, enabling impact analysis and audit trails when changes occur.

Core Features & Use Cases

  • Stable, unique IDs for items and persistent forward/backward traces.
  • Typed links (implements, verifies, validates, satisfies, derives-from) to capture relationships and prove coverage.
  • Orphan detection and evidence retention for regulatory / audit purposes.
  • Exportable reports in Markdown and CSV with diagram-ready visuals.

Quick Start

Provide a Subject, artifact types in scope, and sources, then run the matrix to generate the RTM and export outputs.

Frequently Asked Questions about traceability-matrix

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

FAQPage Schema
How do I create an end-to-end traceability matrix for regulatory audit evidence?

Build a traceability matrix by mapping goals, requirements, stories, tests, and deployed artifacts using deterministic IDs and typed links. The matrix generates bidirectional traces and exports Markdown and CSV reports to provide audit evidence in regulatory contexts.

What is bidirectional tracing and how does it support impact analysis?

Bidirectional tracing uses typed links like implements, verifies, and derives-from to map forward and backward relationships across requirements and tests. This supports impact analysis when changes occur and detects orphaned items lacking proper coverage.

How do I detect orphaned requirements or tests in my software development lifecycle?

Detect orphaned items by generating a traceability matrix with deterministic IDs and typed links across goals, requirements, stories, and tests. The matrix identifies unlinked artifacts to ensure full coverage and evidence retention for compliance audits.

Can I export traceability matrix reports in Markdown and CSV formats?

Yes, you can export traceability matrix reports in both Markdown and CSV formats. The exports include diagram-ready visuals and preserve link rationale to support compliance documentation and audit evidence requirements.

What typed links are needed to prove coverage from goals down to deployed artifacts?

Typed links such as implements, verifies, validates, satisfies, and derives-from capture relationships across goals, requirements, stories, tests, and deployed artifacts. These persistent links prove coverage and preserve rationale for forward and backward traceability views.