traceability-auditor

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

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ref-docs/sdd-stl --skill traceability-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traceability-auditor
Source: https://github.com/ref-docs/sdd-stl/tree/main/.claude/skills/traceability-auditor
Command: npx skills add https://github.com/ref-docs/sdd-stl --skill traceability-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end traceability validation across the SDD lifecycle, ensuring every requirement is mapped to design, task, code, and tests, and surfacing gaps for remediation.

Core Features & Use Cases

  • Validate Requirements → Design coverage (100%) and surface gaps
  • Validate Design → Task mapping
  • Validate Task → Code mapping
  • Validate Code → Test mapping (100% coverage)
  • Gap detection for orphaned requirements and untested code
  • Traceability matrix generation and coverage reporting

Quick Start

Run the traceability-auditor to generate a full traceability matrix for a feature, then review gaps and prepare remediation.

Frequently Asked Questions about traceability-auditor

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

FAQPage Schema
How do I validate that all requirements are traced through design, code, and tests?

Traceability validation ensures every requirement maps to design elements, tasks, code, and tests end-to-end. The auditor detects gaps where requirements lack design coverage, code lacks tests, or orphaned items exist outside the requirement chain, surfacing gaps for remediation across the full SDLC.

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

A traceability matrix is a structured map linking requirements to design, tasks, code, and tests. It provides coverage reporting and gap detection, confirming 100% forward and backward traceability so no requirement goes unmapped and no code lacks test coverage.

Can I detect orphaned requirements and untested code automatically?

Yes. The auditor scans for orphaned requirements with no design mapping and untested code with no test coverage, flagging them for immediate remediation and ensuring complete alignment across requirements, design, tasks, code, and tests.

How do I ensure 100% code coverage ties back to requirements?

The auditor validates code-to-test mapping and traces tests backward to design tasks and forward to requirements, confirming every line of code is tested and every test supports a traced requirement.

What input data do I need to run a traceability audit?

Provide requirements in EARS format, design documentation, task definitions, code, and test definitions. The auditor ingests these artifacts and generates a complete traceability matrix with coverage metrics and gap reports.

When should I run traceability audits in my development lifecycle?

Run audits after requirements are defined, after design is complete, after code is written, and before release to catch gaps early. Continuous audits catch requirements drift and untested code changes throughout the SDLC.