traceability-auditor

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imudak/claudemd-gen --skill traceability-auditor-imudak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traceability-auditor
Source: https://github.com/imudak/claudemd-gen/tree/main/.claude/skills/traceability-auditor
Command: npx skills add https://github.com/imudak/claudemd-gen --skill traceability-auditor-imudak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical problem of ensuring that every requirement is meticulously mapped through the entire development lifecycle, from initial design to final testing, preventing costly gaps and ensuring compliance.

Core Features & Use Cases

  • End-to-End Traceability: Validates mappings from requirements to design, tasks, code, and tests.
  • Gap Detection: Identifies orphaned requirements and untested code.
  • Coverage Reporting: Generates detailed coverage percentages and matrices.
  • Use Case: Before merging a new feature, use this Skill to audit that all user stories have corresponding design documents, implemented code, and passing tests, ensuring no requirements are missed.

Quick Start

Run the traceability-auditor skill to validate requirements coverage for the 'user-authentication' feature.

Frequently Asked Questions about traceability-auditor

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

FAQPage Schema
How do I ensure requirements traceability across the entire SDLC?

Gap detection identifies orphaned requirements and untested code by validating complete traceability mappings across design, tasks, and tests, generating detailed coverage matrices to enforce compliance.

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

Gap detection identifies orphaned requirements and untested code by validating complete traceability mappings across design, tasks, and tests, generating detailed coverage matrices to enforce compliance.

What is requirements coverage reporting and when do I need it?

Requirements coverage reporting calculates mapping percentages across design, tasks, code, and tests to identify missing links, needed before merging features to ensure no requirements are missed and compliance is maintained.

How do I audit EARS requirements for missing mappings before a feature merge?

Auditing EARS requirements for missing mappings before a merge involves validating that all user stories have corresponding design documents, implemented code, and passing tests to ensure complete traceability and prevent costly gaps.

Can I use file search and grep tools to analyze traceability artifacts?

Yes, traceability artifact analysis uses Read, Glob, and Grep tools to scan EARS requirements, design documents, and test files, validating mappings and identifying untested code or orphaned requirements.

What are the limitations of automated traceability auditing?

Automated traceability auditing limitations include relying on existing artifact structures for Read, Glob, and Grep analysis, meaning it can only detect missing mappings and untested code if those artifacts are present in the project.