traceability-auditor

Validate end-to-end traceability across EARS requirements, design, tasks, code, and tests.

12|2|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/nahisaho/CodeGraphMCPServer --skill traceability-auditor-nahisaho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traceability-auditor
Source: https://github.com/nahisaho/CodeGraphMCPServer/tree/main/.claude/skills/traceability-auditor
Command: npx skills add https://github.com/nahisaho/CodeGraphMCPServer --skill traceability-auditor-nahisaho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates complete traceability across requirements, design, tasks, code, and tests, identifying gaps and ensuring 100% coverage.

Core Features & Use Cases

  • Forward Traceability: Map requirements to design, tasks, code, and tests.
  • Backward Traceability: Trace tests back to requirements.
  • Gap Detection: Identify orphaned requirements or untested code.
  • Reporting: Generate traceability matrices and coverage summaries.

Quick Start

Run a traceability audit against the current project artifacts and review the resulting matrix.

Frequently Asked Questions about traceability-auditor

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

FAQPage Schema
How do I validate traceability across requirements, design, code, and tests?

Traceability validation maps requirements forward through design, tasks, and code to tests, then traces tests backward to requirements. This Skill audits end-to-end coverage, generates traceability matrices, and identifies gaps—orphaned requirements or untested code—ensuring 100% coverage across your SDLC artifacts.

What is a traceability matrix and why do I need one?

A traceability matrix is a table linking requirements to design decisions, tasks, code, and test cases. You need one to verify every requirement has corresponding design, implementation, and test coverage, and to detect which requirements lack tests or which code has no backing requirement.

How do I identify orphaned requirements and untested code in my project?

Gap detection analyzes your requirements, design, tasks, code, and test artifacts to flag requirements with no corresponding design or tests, and code with no tracing requirement. This audit surfaces coverage gaps so you can close them before release.

Can I use traceability auditing for compliance and coverage reporting?

Yes. This Skill generates coverage summaries and traceability reports that document what percentage of requirements flow through design, code, and tests. These reports support compliance audits and demonstrate end-to-end coverage across your SDLC.

What's the difference between forward and backward traceability?

Forward traceability maps requirements down to design, tasks, code, and tests—answering 'is this requirement implemented and tested?' Backward traceability traces tests up to requirements—answering 'does this test link to a real requirement?' Both directions catch coverage gaps.

Do I need special tools or formats to run a traceability audit?

The Skill works with your project's existing artifacts—requirements, design documents, task lists, code, and tests. Provide these in their native format; the audit cross-references them to generate matrices and coverage reports without requiring format conversion or external tools.